Access, auth, and limits
Auth is OAuth against Goodie's own sign-in service, with bearer tokens carried in the header. Because authorization runs through your existing Goodie account, scope is inherited rather than configured: the agent sees what your seat sees. There is no API key to generate, rotate or leak into a config file.
The one real friction is documentation. Goodie does not publish the endpoint, the tool inventory, or which pricing tiers include MCP on any public page, so all three are things you confirm after logging in. That is a defensible product decision and an annoying one if you are evaluating Goodie against alternatives before you buy.
Which AI clients can use Goodie AI MCP?
Not every AI assistant supports MCP natively. Per-client picture for Goodie AI:
| Client | Support | Notes |
|---|---|---|
| Claude (Desktop/Web) | Native MCP | — |
| ChatGPT | Native MCP | — |
| Cursor | Native MCP | — |
How to connect Goodie AI MCP to Claude Desktop
Add this block to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Cursor and Codex use a similar schema.
{
"mcpServers": {
"goodie": {
"command": "npx",
"args": ["mcp-remote", "<YOUR_MCP_URL>"]
}
}
}
// HTTP-transport MCP. Get your <YOUR_MCP_URL> from the vendor dashboard.
// Server source: https://mcp.higoodie.com/mcp
// Claude Code (one-liner): claude mcp add goodie <YOUR_MCP_URL> --transport httpSome MCP servers require an API key. Check the source page for setup: mcp.higoodie.com/mcp.
Does Goodie AI MCP cost extra?
Goodie AI has no verified MCP server.
- No published MCP integration was detected at the last check.
- For now, agent workflows depend on the REST API or third-party automation.
What you can do with Goodie AI from an AI agent
Three shapes of agent workflow. Pick the row that matches how you actually use Claude / Cursor / Codex day to day.
Skip the dashboard, ask Claude
- "What changed this week?" answered in seconds
- Quick one-off questions without leaving the editor
- Pipe Goodie AI data into your personal notes / docs without writing a script
Run client analysis at agent speed
- Hand the MCP server to your team — every consultant can ask Claude about any client's Goodie AI account
- Multi-account workflows without context-switching the Goodie AI UI
- Reports you'd normally spend hours on, done before standup
Production agent workflows
- Embed in your internal Codex / Cursor agents that triage Goodie AI data daily
- Combine with other MCP servers in a multi-step agent chain
- Constrain agents to read-only roles to keep production Goodie AI safe
Limits and gotchas
- Official MCP server — published by Goodie AI themselves, so it should track product changes.
- Rate limits: MCP calls count against your underlying Goodie AI API quota. Burst usage from a curious agent can drain a daily allowance fast.
Agent-readiness verdict
A clean OAuth server with a genuinely low-friction setup, held back only by how little Goodie documents publicly. Tool names, counts and plan gating all live behind the login.
Avoid for agent workflows. Goodie AI has no MCP server, public API, or SDK support, making it impossible to integrate into Claude or Cursor-based automation. The tool lacks basic API documentation and structured output capabilities that agents require.
Scored 2026-06-07 by Joonas (TMB).
Goodie AI MCP & API FAQ
Does Goodie AI plan to add an MCP server?+
Sources
- Goodie AI official site: https://www.higoodie.com
- MCP server page: https://mcp.higoodie.com/mcp
Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.
10+ years in digital marketing. I review marketing software for AI-stack fit: real pricing, MCP and API support, and how cleanly each tool drops into an AI agent workflow, cross-checked against verified data and real user feedback.