Connect AI assistants to the Wallboard API using Model Context Protocol (MCP).
With MCP connected, you can talk to your AI assistant in natural language:
The AI finds the right API endpoints and executes them for you - no coding required.
Wallboard supports Dynamic Client Registration (DCR) — clients that support it only need the server URL. No Client ID or Client Secret required.
| Client | DCR | Setup |
|---|---|---|
| Claude Code, Cursor, ChatGPT | Yes | URL only — authentication is fully automatic |
| Claude.ai | No | Create OAuth Client first (Client ID + Secret required) |
| Other MCP clients | Varies | URL only if DCR supported, otherwise manual OAuth config |
| Field | Value |
|---|---|
| Name | Claude AI Assistant (or any name you'll recognize) |
| Redirect URI | https://claude.ai/api/mcp/auth_callback |
| Public | OFF (must be off to get a Client Secret) |
| Field | Value |
|---|---|
| Server URL | https://YOUR_WALLBOARD_SERVER/mcp |
| Client ID | (paste from Step 1) |
| Client Secret | (paste from Step 1) |
Replace YOUR_WALLBOARD_SERVER with your Wallboard server URL (the same URL you use to log in).
Note: If Claude asks for Authorization URL or Token URL, use https://YOUR_WALLBOARD_SERVER/authorize and https://YOUR_WALLBOARD_SERVER/token
Add to your project's .mcp.json (or ~/.claude/.mcp.json for global):
{
"mcpServers": {
"wallboard": {
"type": "http",
"url": "https://YOUR_WALLBOARD_SERVER/mcp"
}
}
}
Replace YOUR_WALLBOARD_SERVER with your Wallboard server URL.
On first use, Claude Code opens your browser for login automatically — no manual OAuth setup needed.
ChatGPT supports Dynamic Client Registration, so setup is URL only — no Client ID or Client Secret required.
| Requirement | Detail |
|---|---|
| Plan | ChatGPT Pro, Plus, Business, Enterprise, or Edu (custom connectors are not available on Free) |
| Developer mode | Enable Developer mode in ChatGPT settings — look under Connectors → Advanced settings (some versions place it under Apps or Security & login). On Business/Enterprise/Edu, a workspace admin must allow custom connectors first. |
| Field | Value |
|---|---|
| Name | Wallboard |
| MCP Server URL | https://YOUR_WALLBOARD_SERVER/mcp |
| Authentication | OAuth |
Replace YOUR_WALLBOARD_SERVER with your Wallboard server URL (the same URL you use to log in).
Enable the Wallboard connector in a chat, then start asking about your Wallboard data.
Any MCP client that supports the MCP Authorization spec works automatically:
| Setting | Value |
|---|---|
| MCP Server URL | https://YOUR_WALLBOARD_SERVER/mcp |
| Transport | Streamable HTTP |
The client discovers OAuth settings automatically via the server's metadata endpoints. Clients that support Dynamic Client Registration (RFC 7591) require no manual OAuth setup.
For clients that need manual OAuth configuration:
| Setting | Value |
|---|---|
| Authorization URL | https://YOUR_WALLBOARD_SERVER/authorize |
| Token URL | https://YOUR_WALLBOARD_SERVER/token |
| Scope | FULL_ACCESS |
"Not authorized" or login keeps appearing
Can't connect to MCP server
/mcp)OAuth client not working (Claude.ai)
https://claude.ai/api/mcp/auth_callback"Create connector" option missing (ChatGPT)