Skip to main content
The Portal.io documentation is available as a Model Context Protocol (MCP) server. If your AI tool supports MCP, you can connect it to Portal.io and ask questions about the API, generate integration code, troubleshoot errors, and look up endpoint details — without leaving your editor or chat. Your AI tool searches Portal.io’s documentation on demand and reads full pages when it needs more detail. The result is responses grounded in the current docs rather than guesses from the model’s training data.

What you can do with it

Once connected, ask your AI tool questions like:
  • “How do I authenticate to the Portal.io API in Python?”
  • “Generate a webhook subscription that triggers on proposal status change.”
  • “What query parameters does the list-proposals endpoint accept?”
  • “Walk me through creating a proposal with multiple areas and options.”
The tool will retrieve the relevant pages from docs.portal.io and use them to answer.
This is different from the AI Builder endpoints in the API. AI Builder is a Portal.io feature for generating proposals. This page is about connecting external AI tools (Claude, ChatGPT, Cursor, etc.) to Portal.io’s documentation.

The connection URL

That’s all you need. Anonymous access; no authentication required.

Set up your AI tool

  1. Open Claude Desktop.
  2. Open Settings (⌘, on macOS, Ctrl , on Windows).
  3. Go to Connectors.
  4. Click Add custom connector.
  5. Set:
    • Name: Portal.io
    • URL: https://docs.portal.io/mcp
  6. Click Add.
Start a new chat and ask a Portal.io API question. Claude will use the connector automatically when relevant.

Try it out

Once connected, try these prompts to confirm the connector is working and to see what it can do:
“How do I authenticate to the Portal.io API? Walk me through getting credentials and signing a request.”Your AI tool should retrieve the authentication overview and signing-requests guide, then explain HMAC signing with example code.
“Write a Node.js Express endpoint that receives a Portal.io webhook for proposal status changes, validates the signature, and logs the payload.”Your AI tool should pull the webhook documentation and event payload schemas, then generate working code.
“What query parameters does GET /public/proposals support, and what does the response look like?”Your AI tool should retrieve the list-proposals reference and summarize the parameters, defaults, and response shape.
“I want to build a workflow that creates a proposal, adds two areas with options, and assigns it to a contact. Outline the API calls in order with example payloads.”Your AI tool should pull the relevant endpoint references and concept pages to plan the sequence.

Troubleshooting

Some AI tools require you to explicitly invoke the connector. Try prefixing your prompt with the connector name (@Portal.io, @portal-io) or asking a question that’s clearly about Portal.io.Also confirm the connector was actually added — open your tool’s connector list and verify Portal.io appears.
Check the URL is https://docs.portal.io/mcp exactly — no trailing slash, no extra path segments.If your tool requires you to choose a transport, select http (not stdio).
The MCP endpoint is auto-generated from the live documentation at docs.portal.io. If you see incorrect information, the underlying docs likely need updating — please file an issue so we can fix the source.

Feedback

This integration is new — your feedback shapes what we improve. If your AI tool isn’t listed here, or you’d like a better experience with a particular tool, let us know.