CivilQuants — Document-pipeline manifest — civilquants MCP Resource
CivilQuants — Document-pipeline manifest
is one of 8 resources on the
civilquants
MCP server. Connect the server and your client can attach it as context.
by client
How to attach CivilQuants — Document-pipeline manifest from your client
- Claude Code civilquants Resource/CivilQuants — Document-pipeline manifest run in your project directory
- Claude Desktop civilquants Resource/CivilQuants — Document-pipeline manifest ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor civilquants Resource/CivilQuants — Document-pipeline manifest ~/.cursor/mcp.json
- VS Code civilquants Resource/CivilQuants — Document-pipeline manifest .vscode/mcp.json
- Zed civilquants Resource/CivilQuants — Document-pipeline manifest ~/.config/zed/settings.json
- Windsurf civilquants Resource/CivilQuants — Document-pipeline manifest ~/.codeium/windsurf/mcp_config.json
- Cline civilquants Resource/CivilQuants — Document-pipeline manifest ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI civilquants Resource/CivilQuants — Document-pipeline manifest ~/.gemini/settings.json
- Grok civilquants Resource/CivilQuants — Document-pipeline manifest .mcp.json (in your project root)
- ChatGPT civilquants Resource/CivilQuants — Document-pipeline manifest Settings → Connectors → Advanced → Developer mode
- Claude.ai civilquants Resource/CivilQuants — Document-pipeline manifest Settings → Connectors → Add custom connector
- LangChain civilquants Resource/CivilQuants — Document-pipeline manifest pip install langchain-mcp-adapters
Other resources on this server
civilquants also offers 11 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.