{
  "markdown": "# MyTelescope Orchestrator MCP Server\n\nA hosted Model Context Protocol (MCP) server from [MyTelescope](https://mytelescope.io).\n\n## What is MyTelescope?\n\nMyTelescope 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.\n\nCore capabilities exposed through this MCP server include:\n\n- **Demand signals** — track how demand for a topic, product, or category evolves over time and geography.\n- **Priorities & share** — calculate relative demand share between competitors, brands, or keywords.\n- **Trajectory & forecasting** — project where demand is heading (short-term and seasonal).\n- **Emerging demand** — surface fast-growing topics before they become obvious.\n- **Signal collections** — query curated, private, or public collections of market signals.\n- **Location intelligence** — scope any analysis to a country, region, or city.\n\nBy 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.\n\n## Authentication\n\nThe 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.\n\n**What happens when you connect:**\n\n1. Your MCP client connects to the server and receives a `401` challenge.\n2. The client opens MyTelescope's hosted login page in your browser.\n3. You sign in with your MyTelescope account (email/password or Google).\n4. The browser redirects back to your client, which receives and stores an access token.\n5. All subsequent MCP calls include the token automatically.\n\n**To use MyTelescope through MCP you need a MyTelescope account.** If you don't have one, sign up at [mytelescope.io](https://mytelescope.io). Tool calls are metered against your account's credit balance, the same way they are inside the MyTelescope web app.\n\n## Client setup\n\nPick 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.\n\n### Option 1 — Claude.ai / Claude Desktop (no config files, UI only)\n\nThis is the easiest path. On Pro, Max, Team, or Enterprise plans (Free allows one custom connector):\n\n1. Open **Claude** → **Settings** → **Connectors**.\n2. Click **+ Add custom connector**.\n3. Paste the URL:\n   ```\n   https://mytelescope-orchestrator-mcp-amjjfcdvoa-uc.a.run.app/mcp\n   ```\n4. Click **Add**.\n5. Click **Connect** on the new \"MyTelescope\" connector — a browser window opens for MyTelescope login; sign in and you're done.\n\nNo JSON files, no `npx`, no Node.js required. Claude handles the OAuth handshake and token refresh automatically.\n\n> On Team/Enterprise workspaces, an **Owner** adds the connector once; members click **Connect** and sign in individually.\n\n### Option 2 — `npx mcp-remote` config (any stdio MCP client)\n\nFor clients that use JSON config files — or older Claude Desktop versions that don't have the Connectors UI — use the [`mcp-remote`](https://www.npmjs.com/package/mcp-remote) bridge. Run on the fly via `npx`, handles OAuth + token caching, requires Node.js 18+.\n\n#### Claude Desktop (`claude_desktop_config.json`)\n\n```json\n{\n  \"mcpServers\": {\n    \"mytelescope\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"mcp-remote\",\n        \"https://mytelescope-orchestrator-mcp-amjjfcdvoa-uc.a.run.app/mcp\"\n      ]\n    }\n  }\n}\n```\n\n#### Claude Code (CLI)\n\n```bash\nclaude mcp add --transport http mytelescope \\\n  https://mytelescope-orchestrator-mcp-amjjfcdvoa-uc.a.run.app/mcp\n```\n\nIf your version of Claude Code doesn't support `--transport http` yet, use the same `npx mcp-remote` config as Claude Desktop above.\n\n#### Cursor (`~/.cursor/mcp.json`)\n\nCursor supports remote servers directly — no `mcp-remote` bridge needed:\n\n```json\n{\n  \"mcpServers\": {\n    \"mytelescope\": {\n      \"url\": \"https://mytelescope-orchestrator-mcp-amjjfcdvoa-uc.a.run.app/mcp\"\n    }\n  }\n}\n```\n\n#### Windsurf / other stdio-only clients\n\nUse the same `npx mcp-remote` snippet shown for Claude Desktop.\n\n### First-run login\n\nWhichever 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.\n\n## Registry\n\nThis server is listed on the [official MCP Registry](https://registry.modelcontextprotocol.io/) under the namespace `io.github.mytelescope/orchestrator`.\n\n## Support\n\n- Issues: open a GitHub issue on this repo\n- Contact: theesh@mytelescope.io\n\n## License and terms of use\n\n**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.\n\n**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:\n\n- The MyTelescope orchestrator service or any hosted MCP endpoint operated by MyTelescope\n- MyTelescope's APIs, demand signals, forecasts, or any data served through them\n- The MyTelescope brand, trademarks, or logos\n\nUse of the MyTelescope service requires a MyTelescope account and is governed by the [MyTelescope Terms of Service](https://mytelescope.io/terms) and [Privacy Policy](https://mytelescope.io/privacy). Tool calls made through this MCP server consume credits from your MyTelescope account.\n\nSee [LICENSE](./LICENSE) for the full MIT text applied to this repository.\n",
  "bytes": 5838,
  "sha": "25a614832b591ac26b49f5e581d87feedfb89caacd060ec7e1f6e171241d16fc",
  "repo_slug": "mytelescope/mcp-orchestrator",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_mytelescope_mytelescope_52ac356d/readme"
}