Headless Service — docs mcp MCP Resource
Headless Service
is one of 49 resources on the
docs mcp
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Headless Service from your client
- Claude Code docs mcp Resource/Headless Service run in your project directory
- Claude Desktop docs mcp Resource/Headless Service ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor docs mcp Resource/Headless Service ~/.cursor/mcp.json
- VS Code docs mcp Resource/Headless Service .vscode/mcp.json
- Zed docs mcp Resource/Headless Service ~/.config/zed/settings.json
- Windsurf docs mcp Resource/Headless Service ~/.codeium/windsurf/mcp_config.json
- Cline docs mcp Resource/Headless Service ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI docs mcp Resource/Headless Service ~/.gemini/settings.json
- Grok docs mcp Resource/Headless Service .mcp.json (in your project root)
- ChatGPT docs mcp Resource/Headless Service Settings → Connectors → Advanced → Developer mode
- Claude.ai docs mcp Resource/Headless Service Settings → Connectors → Add custom connector
- LangChain docs mcp Resource/Headless Service pip install langchain-mcp-adapters
Other resources on this server
- Agent Team Api
- Agent Team Events
- Architecture
- Engine Commands
- Engine Testing
- Eval Runner
- How Tandem Works
- Protocol Matrix
- Spawn Policy
- Tools
- Tui Commands
- Agent Teams
- Agents And Sessions
- Channel Integrations
- Configuration
- Control Panel
- First 10 Minutes
- Headless Deployment
- Learn Walkthroughs
- Overview
- Settings And Safety
- Troubleshooting
- Tui Guide
- Workflows
- Agent Runtime Guide
- Agent Workflow Mission Quickstart
- Automation Examples For Teams
- Automation V2 Webhooks
- Autonomous Coding Agents Github Projects
- Browser Setup And Testing
- Choosing Providers And Models For Agents
- Creating And Running Workflows And Missions
- Destination Router
- Destinations
- Engine Authentication For Agents
- Enterprise Client Onboarding Runbook
- Enterprise Data Governance
- External Sources
- Incident Monitor
- Incident Monitor External Log Intake
docs mcp also offers 3 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.