Connect an AI assistant

The AutoRFP.ai MCP server lets an AI assistant search and update your approved content, read projects and their requirements, and update requirement answers, signed in as a user with that user’s existing permissions. It is available on every AutoRFP.ai plan at no extra cost.

Server URLs

Use the server URL for the region your AutoRFP.ai workspace is hosted in. If you are not sure, ask your workspace admin.

Connect a client

• Claude (web, desktop and Claude Code): add a custom connector and paste the URL.
• ChatGPT: turn on developer mode, then add a connector with the URL.
• Cursor and other MCP clients: add the URL as a remote server, for example in mcp.json:

{
  "mcpServers": {
    "autorfp": { "url": "https://api.autorfp.ai/mcp" }
  }
}

The first time the assistant calls AutoRFP.ai, a browser window asks you to log in and approve access. For which connectors to add alongside it, see Claude connectors for bid teams.

Sign-in and permissions

Interactive clients sign the user in with OAuth 2.0 Authorization Code with PKCE and act with that user’s permissions. A token never sees more than the user can see in the app. Ask only for the scopes your tools need: the :read scopes cannot change anything. OAuth clients can only request the scopes marked MCP in the scope reference; asking for a REST-only scope fails client registration. The write tools also need write scopes your organisation has enabled.

For a script or a server-side agent, the API key you use for the REST API also works as the bearer token.

tools/list only returns the tools your token’s scopes allow. See the MCP tools reference.

Build your own agent

The server speaks Streamable HTTP: JSON-RPC 2.0 messages sent with POST to the /mcp URL of your region. It is stateless, so each request stands alone. It offers tools only, with no resources or prompts.

Send the access token, the protocol version and both response media types with every request. Start with initialize, then tools/list to see the tools your scopes allow, then tools/call.

curl https://api.autorfp.ai/mcp \
  -X POST \
  -H "Authorization: Bearer $AUTORFP_ACCESS_TOKEN" \
  -H "MCP-Protocol-Version: 2025-11-25" \
  -H "Accept: application/json, text/event-stream" \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Clients discover the sign-in endpoints themselves from the OAuth server metadata and the protected resource metadata.

Errors

A tool call that fails, for example for a missing scope or an item that does not exist, returns a normal tool result with isError: true and a text message. A missing or invalid token returns HTTP 401 with a WWW-Authenticate header. The endpoint allows 600 requests per minute per IP address. See Errors.

Try it

To try the MCP server without an account, book a demo. Plans and the 30-day money-back guarantee are on the pricing page.