Project MonetRequest demo
Home/Blog/How to Use StackScope API & MCP with Claude, ChatGPT and Cursor

Automation · Project Monet Briefing

How to Use StackScope API & MCP with Claude, ChatGPT and Cursor

StackScope exposes the same launch-time technographic data through a conventional HTTP API and a remote MCP server for AI assistants.

Published 2026-09-01 · Updated 2026-09-01 · By Project Monet Editorial Team

StackScope branching to HTTP API for production workflows and MCP for Claude, ChatGPT and Cursor.

01

Connect through MCP

StackScope's official remote MCP endpoint is https://mcp.stackscope.dev. Its documentation covers Claude, ChatGPT, Cursor, Claude Code, VS Code and other MCP-capable clients.

  • Claude and ChatGPT can add the endpoint as a custom connector.
  • Claude Code can add it over HTTP and then complete sign-in through its MCP flow.
  • Cursor and compatible editors can use the remote URL in MCP configuration.

02

Use the HTTP API for deterministic workflows

The HTTP API uses bearer authentication with scoped keys. Current documentation exposes lookup, technology catalogues, launch feeds, trends, exports and watch management depending on the plan and key permissions.

  • Keep API keys out of client-side code and repositories.
  • A 401 generally indicates missing or invalid authentication; 403 indicates a plan or scope limitation.
  • Prefer the API for scheduled jobs, database ingestion and repeatable production automation.

03

Understand credits and distinct launches

StackScope meters requests and newly accessed launch records separately. One normal data call costs one request credit; a new launch record first accessed in the billing period also counts against the plan's distinct-launch allowance.

  • Re-reading the same launch during the period does not consume another distinct-launch slot.
  • A large export can use one request credit but many distinct-launch slots.
  • MCP can surface the estimated cost before a large result and wait for approval.

04

Choose API vs MCP by job

MCP is useful for exploratory human-in-the-loop research, while the API is better for proven repeatable workflows. A practical pattern is to explore a niche conversationally, then turn a useful filter into a watch or API job.

  • Review unknown URLs before automatically fetching or rendering them.
  • Use scoped credentials for each internal service.
  • Keep sales or publishing actions separate from raw data retrieval and qualification.

Sources

Primary and supporting sources

Facts were rechecked against the linked sources immediately before publication. Pricing, product availability and rollout status can change.

Project Monet

Useful signals. Clear decisions. Better digital work.

Project Monet turns relevant shifts in AI, creator tools and the web into practical context—and builds focused websites for businesses ready to grow.

Request a free homepage concept