MCP for agents

ScopeDocs exposes the same source-linked project record to agents through the Model Context Protocol (MCP). Humans ask in ScopeDocs; agents pull the same cited decisions for Cursor, Claude Code, ChatGPT, and custom stacks.

Discovery

Machine-readable document: https://scopedocs.ai/.well-known/mcp.json

yourcompany.mcp.scopedocs.ai

Guide: MCP for engineering documentation · markdown · Homepage: #agents

Auth and permissions

Sign in at app.scopedocs.ai, connect integrations with read-only OAuth, then use the workspace MCP URL shown in the product. There is no public anonymous MCP endpoint for customer workspaces.

Example auth header pattern after you obtain a workspace token from the product:

Authorization: Bearer <scopedocs_workspace_token>

MCP FAQ

Which agents work with ScopeDocs MCP?

Any MCP-capable client including Cursor, Claude Code, ChatGPT, and custom agent stacks when configured for your workspace.

Does MCP replace humans reading docs?

No. MCP extends the same cited record to agents. See docs hub and MCP features.

Markdown version · Quickstart · Privacy · Agents use case

Concept guides

Where to go next

Pick a path. Each link is a short stop on the same source-linked record.

Site directory for agents

Every core URL on scopedocs.ai. Traverse via sitemap.xml, sitemap.md, llms.txt, or llms-full.txt.

Product and company pages
PageHTMLMarkdown twin
Homescopedocs.aiindex.md
Product/productproduct.md
Features/featuresfeatures.md
Solutions/solutions
Pricing/pricingpricing.md
About/aboutabout.md
About us/about-us
Team/teamteam.md
Blog/blog
Privacy/privacyprivacy.md
Terms/terms-of-serviceterms-of-service.md
Docs and agent files
ResourceURL
Docs hub/docs · docs.md
Quickstart/docs/quickstart · quickstart.md
MCP for agents/docs/mcp · mcp.md
MCP discovery/.well-known/mcp.json
AGENTS.md/AGENTS.md
llms.txt/llms.txt
llms-full.txt/llms-full.txt
Sitemap/sitemap.xml · /sitemap.md

Concept guides

Team profiles

Homepage sections

Solutions use cases

Blog topic hubs

Featured blog posts