MCP Server now connects to Claude.ai with one click

You can now add the PingAura MCP Server to Claude.ai as a custom connector — no API key needed. Click Add custom connector in Claude, paste https://www.pingaura.ai/api/mcp, and approve on a consent screen on pingaura.ai. The token Claude receives is bound to the account you pick.

What's new

• OAuth 2.1 connector flow. Standards-based — discovery, dynamic client registration, PKCE, audience-bound JWTs. Same setup as connecting Linear, Atlassian, or any other OAuth-based connector in Claude.
• Account picker on consent. If you belong to a personal account plus one or more team accounts, the consent screen lets you pick which one Claude operates on. The token never sees the others.
• Read or read+write permission. Default is read+write; uncheck "Modify your data" on the consent screen if you only want Claude to inspect things.
• Tool expansion: 26 → 29 tools. Three additions from splitting tools whose destructiveness depended on input args, so Claude can show the right confirmation prompt automatically:
  • archive-prompt + restore-prompt (was one tool with a restore flag)
  • create-prompt-topic, update-prompt-topic, delete-prompt-topic (was one tool with an action enum)
  • archive-article (renamed from delete-article — matches actual behavior; status set to archived, not hard-deleted)

API key auth still works

If you're connecting from Claude Desktop, Cursor, Codex, VS Code, Windsurf, Gemini CLI, or anything else that takes a header, the existing Authorization: Key pa_… flow is unchanged. OAuth is for Claude.ai's hosted connector experience specifically.

Under the hood

• Resource server: https://www.pingaura.ai/api/mcp
• RFC 9728 protected-resource metadata: https://www.pingaura.ai/.well-known/oauth-protected-resource
• Audience binding via custom JWT claim — tokens issued for the MCP server cannot be replayed against other endpoints.
• Scope downgrade enforced server-side at token-mint time, regardless of what the client requested.

Get started

• New users: see OAuth 2.1 Server for the consent flow walkthrough.
• Existing API key users: nothing changes, docs here.
• Technical setup, all 29 tools listed, troubleshooting: MCP Server docs.