MyTelescope
MyTelescope demand intelligence: signals, forecasts, competitor share, and emerging trends.
Open source Repository Open in the app JSON README (API)
About
MyTelescope demand intelligence: signals, forecasts, competitor share, and emerging trends.
Details
- Kind
- MCP servers
- Topic
- No topic detected
- Publisher
- mytelescope
- Origin
- official
- Category
- ferramentas
- Transport
- http
- Version
- 0.1.0
- Last push
- 2026-04-23T09:46:43Z
- Repository state
- ativo
- License
- NOASSERTION
- Added
- 2026-08-29 03:02:07
- Updated
- 2026-08-29 03:02:07
- Origin id
io.github.MyTelescope/mytelescope
README
# MyTelescope Orchestrator MCP Server
A hosted Model Context Protocol (MCP) server from [MyTelescope](https://mytelescope.io).
## What is 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:
- **Demand signals** — track how demand for a topic, product, or category evolves over time and geography.
- **Priorities & share** — calculate relative demand share between competitors, brands, or keywords.
- **Trajectory & forecasting** — project where demand is heading (short-term and seasonal).
- **Emerging demand** — surface fast-growing topics before they become obvious.
- **Signal collections** — query curated, private, or public collections of market signals.
- **Location intelligence** — scope any analysis to a country, region, or city.
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.
## Authentication
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:**
1. Your MCP client connects to the server and receives a `401` challenge.
2. The client opens MyTelescope's hosted login page in your browser.
3. You sign in with your MyTelescope account (email/password or Google).
4. The browser redirects back to your client, which receives and stores an access token.
5. All subsequent MCP calls include the token automatically.
**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.
## Client setup
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.
### Option 1 — Claude.ai / Claude Desktop (no config files, UI only)
This is the easiest path. On Pro, Max, Team, or Enterprise plans (Free allows one custom connector):
1. Open **Claude** → **Settings** → **Connectors**.
2. Click **+ Add custom connector**.
3. Paste the URL:
```
https://mytelescope-orchestrator-mcp-amjjfcdvoa-uc.a.run.app/mcp
```
4. Click **Add**.
5. Click **Connect** on the new "MyTelescope" connector — a browser window opens for MyTelescope login; sign in and you're done.
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.
### Option 2 — `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`](https://www.npmjs.com/package/mcp-remote) bridge. Run on the fly via `npx`, handles OAuth + token caching, requires Node.js 18+.
#### Claude Desktop (`claude_desktop_config.json`)
```json
{
"mcpServers": {
"mytelescope": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mytelescope-orchestrator-mcp-amjjfcdvoa-uc.a.run.app/mcp"
]
}
}
}
```
#### Claude Code (CLI)
```bash
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 (`~/.cursor/mcp.json`)
Cursor supports remote servers directly — no `mcp-remote` bridge needed:
```json
{
"mcpServers": {
"mytelescope": {
"url": "https://mytelescope-orchestrator-mcp-amjjfcdvoa-uc.a.run.app/mcp"
}
}
}
```
#### Windsurf / other stdio-only clients
Use the same `npx mcp-remote` snippet shown for Claude Desktop.
### First-run login
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.
## Registry
This server is listed on the [official MCP Registry](https://registry.modelcontextprotocol.io/) under the namespace `io.github.mytelescope/orchestrator`.
## Support
- Issues: open a GitHub issue on this repo
- Contact: theesh@mytelescope.io
## License and terms of use
**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:
- The MyTelescope orchestrator service or any hosted MCP endpoint operated by MyTelescope
- MyTelescope's APIs, demand signals, forecasts, or any data served through them
- The MyTelescope brand, trademarks, or logos
Use 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.
See [LICENSE](./LICENSE) for the full MIT text applied to this repository.