pruva-mcp

Remote Model Context Protocol server for Pruva. Connect your AI assistant to your Pruva products, features, and documents over HTTPS — no install, no API keys.

Endpoint

https://mcp.pruva.ai/api/mcp

Authentication is handled by your MCP client over OAuth 2.1 against the Pruva backend. The first tool call opens a browser tab where you approve access; the token is then stored by your client and reused.

Related MCP server: productplan-mcp-server

Setup

Claude Code

claude mcp add --transport http pruva https://mcp.pruva.ai/api/mcp

Claude Desktop

In claude_desktop_config.json:

{
  "mcpServers": {
    "pruva": {
      "type": "http",
      "url": "https://mcp.pruva.ai/api/mcp"
    }
  }
}

Cursor

In .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

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

Other clients

Any MCP client that speaks Streamable HTTP with OAuth 2.1 works. Point it at the endpoint — discovery happens automatically via /.well-known/oauth-protected-resource.

Tools

Resources

Security

• No long-lived secrets to manage — auth runs through the standard OAuth flow in your browser.

• Tokens are stored by your MCP client, not by this server.

• Every API call is re-validated against the Pruva backend.

• Revoke access any time from your Pruva account settings.

Links

• Pruva

• pruva-cli — terminal companion

• Model Context Protocol

Issues

GitHub Issues

License

MIT