Data · Remote MCP server
StitchAPI Docs
Search and read the StitchAPI docs: search_docs finds relevant sections, get_doc reads a page.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.stitchapi/docs- Version
- 1.1.0
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-07-08
- Updated
- 2026-07-08
- Publisher
- dev.stitchapi
- Namespace
- Namespace verified by the MCP Registry via the domain stitchapi.dev · how
- Website
- stitchapi.dev
- Repository
- github.com/rejifald/StitchAPI
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://stitchapi.dev/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- stitchapi-docs 1.0.0 · protocol 2025-06-18
- Tools discovered
- 2:
search_docs,get_doc - Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @stitchapi/docs-mcp | 1.0.0-rc.5 | stdio |
How to connect StitchAPI Docs
StitchAPI Docs is a remote MCP server: there is nothing to install. Its endpoint is https://stitchapi.dev/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @stitchapi/docs-mcp version 1.0.0-rc.5. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @stitchapi/docs-mcp@1.0.0-rc.5.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"docs": {
"command": "npx",
"args": [
"-y",
"@stitchapi/docs-mcp@1.0.0-rc.5"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More data servers
| Server | Runs |
|---|---|
| Stellar Agent SearchDiscover and rank Stellar 8004 agents with a read-only MCP server and fail-closed contract probes. | Local · stdio |
| Stellar MCPStellar ledger and account data from Horizon. No key required. | Local · stdio |
| Stipple - Government TendersSearch AU/NZ government tenders and rank a shortlist against company capabilities. | Remote · HTTPLive check: ✓ handshake |
| Stipple - Reference VerificationFact-check citations: resolve, match, support claims. Arithmetic rechecked. Free to start. | Remote · HTTPLive check: ✓ handshake |
| Stompy - AI Memory for Claude & MCP AgentsPersistent AI memory with semantic search, conflict detection, and ticketing. | Remote · HTTPLive check: sign-in required |
| Store BuilderDesign, fill with real store data, render and publish Store Builder pages from an AI agent. | Local · stdio |
| Storebridge MCPRemote MCP connector for App Store + Google Play data via StoreBridge API. No auth required. | Remote · HTTPLive check: ✓ handshake |
| Storting NoStortinget (Norwegian Parliament) open data MCP - data.stortinget.no. | Remote · HTTPLive check: ✓ handshake |