Server data from the Official MCP Registry
MyTelescope demand intelligence: signals, forecasts, competitor share, and emerging trends.
MyTelescope demand intelligence: signals, forecasts, competitor share, and emerging trends.
Remote endpoints: streamable-http: https://mytelescope-orchestrator-mcp-amjjfcdvoa-uc.a.run.app/mcp
Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.
Endpoint verified · Requires authentication · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"io-github-mytelescope-mytelescope": {
"url": "https://mytelescope-orchestrator-mcp-amjjfcdvoa-uc.a.run.app/mcp"
}
}
}From the project's GitHub README.
A hosted Model Context Protocol (MCP) server from MyTelescope.
MyTelescope is a demand intelligence platform for marketers and growth teams. It turns real-world search and behavioral signals into decisions — which keywords are rising, which markets are heating up, which competitors are gaining share, and where to place the next bet.
Core capabilities exposed through this MCP server include:
By connecting MyTelescope to an MCP-compatible client (Claude Desktop, Claude Code, Cursor, etc.), you can ask questions like "is demand for X rising in Germany?" or "who's gaining share in the running-shoe category this quarter?" and get grounded, data-backed answers inside your normal workflow.
The server uses OAuth 2.1 with PKCE backed by Firebase. You do not need to paste an API key — your MCP client handles the flow automatically.
What happens when you connect:
401 challenge.To use MyTelescope through MCP you need a MyTelescope account. If you don't have one, sign up at mytelescope.io. Tool calls are metered against your account's credit balance, the same way they are inside the MyTelescope web app.
Pick the path that matches how you use Claude (or your MCP client of choice). All paths end at the same OAuth login screen on first connection.
This is the easiest path. On Pro, Max, Team, or Enterprise plans (Free allows one custom connector):
https://mytelescope-orchestrator-mcp-amjjfcdvoa-uc.a.run.app/mcp
No JSON files, no npx, no Node.js required. Claude handles the OAuth handshake and token refresh automatically.
On Team/Enterprise workspaces, an Owner adds the connector once; members click Connect and sign in individually.
npx mcp-remote config (any stdio MCP client)For clients that use JSON config files — or older Claude Desktop versions that don't have the Connectors UI — use the mcp-remote bridge. Run on the fly via npx, handles OAuth + token caching, requires Node.js 18+.
claude_desktop_config.json){
"mcpServers": {
"mytelescope": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mytelescope-orchestrator-mcp-amjjfcdvoa-uc.a.run.app/mcp"
]
}
}
}
claude mcp add --transport http mytelescope \
https://mytelescope-orchestrator-mcp-amjjfcdvoa-uc.a.run.app/mcp
If your version of Claude Code doesn't support --transport http yet, use the same npx mcp-remote config as Claude Desktop above.
~/.cursor/mcp.json)Cursor supports remote servers directly — no mcp-remote bridge needed:
{
"mcpServers": {
"mytelescope": {
"url": "https://mytelescope-orchestrator-mcp-amjjfcdvoa-uc.a.run.app/mcp"
}
}
}
Use the same npx mcp-remote snippet shown for Claude Desktop.
Whichever path you use, the first connection opens your browser at MyTelescope's hosted login page. Sign in with your MyTelescope account; your token is cached (by Claude, or by mcp-remote under ~/.mcp-auth/) so subsequent sessions are silent until the token expires.
This server is listed on the official MCP Registry under the namespace io.github.mytelescope/orchestrator.
The MIT license in this repository covers only the contents of this repository — the README, the server.json manifest, and example snippets. You are free to copy, fork, or adapt those files.
The MyTelescope service is a paid SaaS product and is not free. The MIT license does not grant any right to use, access, or redistribute:
Use of the MyTelescope service requires a MyTelescope account and is governed by the MyTelescope Terms of Service and Privacy Policy. Tool calls made through this MCP server consume credits from your MyTelescope account.
See LICENSE for the full MIT text applied to this repository.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.