Koskamo

MyTelescope MCP

MyTelescope is a demand intelligence platform that turns real-world search and behavioral signals into decisions. This MCP server allows agents to query rising keywords, market trends, competitor share, and emerging opportunities by connecting to an MCP-compatible client like Claude Desktop or Cursor.

Endpoint and access

API key: create a key with the vendor first; your client sends it as an authorization header on every request.

MyTelescope MCP logo, by MyTelescopeCommunity listingStreamable HTTPAPI keyEndpoint checked 2026-11-06Published by MyTelescope
You need:You do not need to paste an API key — your MCP client handles the flow automatically.To use MyTelescope through MCP you need a MyTelescope account.Tool calls are metered against your account's credit balance
MCP endpoint (Streamable HTTP)
https://mytelescope-orchestrator-mcp-amjjfcdvoa-uc.a.run.app/mcp
Vendor documentation

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Check if demand for a product is rising in a specific region
  • Identify which competitors are gaining share in a category
  • Discover emerging market trends and keywords
  • Get data-backed answers for marketing decisions

Source and maintenance

Community listingRegistry 0.1.0
mcp-registry: io.github.MyTelescope/mytelescope@0.1.0Source repository
Maintenance checked

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-06: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
141 ms
95th percentile latency
141 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 141 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http mytelescope-mcp https://mytelescope-orchestrator-mcp-amjjfcdvoa-uc.a.run.app/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add mytelescope-mcp --url https://mytelescope-orchestrator-mcp-amjjfcdvoa-uc.a.run.app/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable mytelescope-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "mytelescope-mcp": {
      "url": "https://mytelescope-orchestrator-mcp-amjjfcdvoa-uc.a.run.app/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "mytelescope-mcp": {
      "type": "streamableHttp",
      "url": "https://mytelescope-orchestrator-mcp-amjjfcdvoa-uc.a.run.app/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start mytelescope-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "mytelescope-mcp": {
      "type": "http",
      "url": "https://mytelescope-orchestrator-mcp-amjjfcdvoa-uc.a.run.app/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http mytelescope-mcp https://mytelescope-orchestrator-mcp-amjjfcdvoa-uc.a.run.app/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://mytelescope-orchestrator-mcp-amjjfcdvoa-uc.a.run.app/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "mytelescope-mcp": {
      "serverUrl": "https://mytelescope-orchestrator-mcp-amjjfcdvoa-uc.a.run.app/mcp"
    }
  }
}

Let your agent find its tools

Find servers like MyTelescope MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 5,552