Forums
Engineer turned founder, figuring out distribution
Hey PH - I'm Soumyadeep. Building Ekamoira, tools for search visibility.
Engineering background. Spent the last year figuring out how AI is reshaping search and what businesses should actually do about it.
What Ekamoira Search Console MCP really does and who is it built for
Most people export GSC data to spreadsheets, write formulas, maybe build a Looker dashboard. It works, but it's slow and you lose context the moment you have a new question.
We built an MCP server that connects Google Search Console directly to Claude. No exports. No dashboards. Just ask questions in plain English:
what is the best in class way to let claude / codex etc view the browser?
if i use claude or codex, i constantly am screen capping to show bad padding / alignment / whatever. is there a defacto way to let claude or codex tool call to see the browser or render a page for themselves?
Built an MCP for Google Search Console → AI workflows (intro + looking for feedback)
Hi everyone I m Soumyadeep
Co-Founder at Ekamoira. Long-time SEO / agency operator turned product builder.
After years of running SEO and content teams, we kept running into the same problem:
GSC data is critical, but painfully slow to analyze and hard to plug into modern AI workflows.
So we built our first product: a Google Search Console MCP (Model Context Protocol) that lets AI tools query, analyze, and reason over GSC data directly instead of exporting CSVs or building one-off scripts.
The idea is simple:
