What the MCP server is
ResponseHub runs a Model Context Protocol (MCP) server. MCP is the standard way an AI assistant connects to an outside system, so connecting ResponseHub to an assistant lets you ask it things like “what does our policy say about data retention?” or “start a questionnaire from this spreadsheet” and have it work against your own knowledge base rather than guessing.
Once connected, the assistant can read and write the same material you see in ResponseHub — your sources, your knowledge base items, your questionnaires and your RFPs.
The server URL
Section titled “The server URL”https://app.responsehub.io/mcpYou can copy it from inside ResponseHub: open API from your account menu, then the MCP tab. That screen also carries the ready-made command for command-line clients.
What a connected assistant can do
Section titled “What a connected assistant can do”- Ask questions and get answers with confidence scores and citations.
- Search the knowledge base, and create, update or approve items.
- List, create, download and delete questionnaires and RFPs.
- Upload and manage source documents.
Each of those is a tool the assistant chooses to call. The tool reference lists all 21 of them and what each one takes.
Two ways to connect
Section titled “Two ways to connect”| You are using | How you connect |
|---|---|
| Claude.ai, ChatGPT | Add ResponseHub as a custom connector — you sign in and approve access, with no token to manage. |
| Claude Code, Cursor, the Claude API, other clients | Create an API token and pass it as a header. |
Assistants act as you
Section titled “Assistants act as you”An assistant connected to ResponseHub is not a separate user with its own permissions. It sees exactly what your account role lets you see, it can only change what you could change, and every change it makes is recorded in the audit trail against your name. If your role is read-only, a connected assistant is read-only too.
Everything is scoped to one account. If you belong to more than one, the connection is bound to a single account rather than reaching across them — see permissions and safety.
How this differs from the API
Section titled “How this differs from the API”The JSON API and the MCP server cover much of the same ground, and both use the same API tokens. The difference is who is calling:
- The API is for software you write. You choose the endpoints, handle the responses, and build whatever you are building.
- The MCP server is for an assistant to call on your behalf, in conversation. You describe what you want; the assistant picks the tools.
The MCP server exposes a deliberately smaller surface than the API — the things an assistant can usefully do — so anything it does not cover is an API job.