MCP server

MCP is an open protocol that lets an AI assistant call tools on your behalf. The Prokure MCP server will let an assistant read your matched opportunities, give feedback on them, and manage your company profile and digest settings — without you writing any API glue.

Connection


Endpoint	`https://mcp.prokure.ca`
Transport	Streamable HTTP
Authentication	OAuth sign-in with your Prokure account

There is no separate credential to create. You sign in with the Prokure account you already have, and the client holds the resulting authorisation — no API key is copied into a config file.

Planned tools

Tool	Does
`search_opportunities`	Find matched opportunities.
`get_opportunity`	Read one opportunity, including the verdict rationale and match scores.
`give_feedback`	Agree or disagree with a verdict, with a reason.
`archive_opportunity`	Archive an opportunity.
`unarchive_opportunity`	Restore an archived opportunity.
`get_company_profile`	Read the company profile, product catalog, and certifications.
`update_company_profile`	Change the company profile, product catalog, and certifications.
`get_digest_settings`	Read the digest schedule and recipients.
`update_digest_settings`	Change the digest schedule and recipients.

These map onto the same six scopes the REST API uses — see Scopes. A tool that reads opportunities needs opportunities:read; one that writes settings needs settings:write. Nothing the MCP server can do sits outside that vocabulary.

Client configuration

claude mcp add --transport http prokure https://mcp.prokure.ca

Then run /mcp inside Claude Code to complete the OAuth sign-in.

Add Prokure as a custom connector in settings, paste https://mcp.prokure.ca as the server URL, and complete the OAuth sign-in when prompted.

Most clients take a JSON config of this shape:

{
  "mcpServers": {
    "prokure": {
      "type": "http",
      "url": "https://mcp.prokure.ca"
    }
  }
}

Consult your client’s documentation for where that file lives and how it prompts for OAuth.