Connect ToolGrid MCP
ToolGrid MCP lets AI clients discover and run ToolGrid tools through the TOOLGRID API GATEWAY. Billing uses your existing Developer API subscription and API credit wallet — there is no separate MCP plan.
This guide is for customers integrating on their own machines against production. You do not need ToolGrid source code, a local backend, or server secrets.
Product overview: toolgrid.io/mcp · Connection settings: Dashboard → MCP
Choose your client
| Client | Auth | Where secrets live |
|---|---|---|
| Cursor (or similar IDE) | Bearer API key → https://api.toolgrid.io/mcp | MCP config / env on your machine only |
| ChatGPT (custom MCP) | OAuth 2.1 + PKCE | Browser consent on ToolGrid; ChatGPT stores tokens |
Never paste a raw tg_api_… key into ChatGPT chat. Prefer OAuth for any cloud AI client.
1. Prerequisites
- Sign in at toolgrid.io.
- Open Dashboard → TOOLGRID API GATEWAY and confirm an active Developer API subscription.
- Confirm API credits > 0 on Credits (billing docs).
- For Cursor: create a key at Keys and copy
tg_api_…once into a password manager. - Open Dashboard → MCP and confirm status is Enabled with resource URL
https://api.toolgrid.io/mcp.
2. Cursor — remote MCP (API key)
Connect Cursor on your laptop to production ToolGrid MCP. Use any personal or work project — you do not need the ToolGrid repository.
- Open Cursor → Settings → MCP (or your user-level MCP JSON).
- Add a remote HTTP / Streamable HTTP server pointing at production:
{
"mcpServers": {
"toolgrid": {
"url": "https://api.toolgrid.io/mcp",
"headers": {
"Authorization": "Bearer tg_api_YOUR_KEY"
}
}
}
}- Replace
tg_api_YOUR_KEYwith your key from Dashboard → Keys. - Exact JSON field names can vary by Cursor version. If the UI offers an HTTP / SSE / Streamable HTTP URL field, paste
https://api.toolgrid.io/mcpand set the Bearer header there. - Reload MCP servers or restart Cursor after saving.
- Do not clone ToolGrid or run a local backend just to connect. If your Cursor build cannot add a remote URL MCP server, use the ChatGPT OAuth path below.
Confirm tools appear
In Agent/chat for that project, ToolGrid should expose:
- toolgrid_search_tools
- toolgrid_get_tool_schema
- toolgrid_preview_price
- toolgrid_execute
- toolgrid_create_job
- toolgrid_get_job
- toolgrid_balance
Try it (example prompts)
- Use ToolGrid MCP toolgrid_balance and tell me my remaining API credits. — should match Dashboard → Credits.
- Call toolgrid_search_tools with query "password" and limit 5.
- Call toolgrid_get_tool_schema for password_generator.
- Call toolgrid_preview_price for password_generator (useAI false). — no charge.
- Call toolgrid_execute for password_generator, count 1, length 16. Show the password and billing. — then check Usage and Credits: balance should decrease once.
3. ChatGPT — custom MCP (OAuth)
Use your ChatGPT account on a plan/workspace that allows custom MCP. Authentication is OAuth — no API key in the chat.
- In ChatGPT, open Apps / Plugins / MCP settings.
- Add a custom MCP server:
- Name: ToolGrid
- Server URL:
https://api.toolgrid.io/mcp - Authentication: OAuth (not “no auth”, not paste API key)
- Save. ChatGPT discovers OAuth and may register a client automatically.
- Browser opens
https://www.toolgrid.io/oauth/mcp/consent. Sign in with the same ToolGrid account that has the Developer API subscription. - Review client, redirect URI, and scopes — then click Approve.
- Return to ChatGPT. Tokens are exchanged server-side; raw API keys are never shared.
Conversation checks
Start a new chat, attach/select ToolGrid if required, then:
- Search: toolgrid_search_tools with query
password. - Schema + preview for
password_generator. - Execute once (count 1) and confirm credits charged.
- Call
toolgrid_balance.
On ToolGrid, open Dashboard → MCP — Connected OAuth grants should list the ChatGPT client. After a successful execute, Usage and Credits update. Revoke the grant to block further calls until re-auth.
4. What agents can call
| Tool | Purpose |
|---|---|
| toolgrid_search_tools | Discover tools in the live gateway registry |
| toolgrid_get_tool_schema | Fields and schemas for a tool |
| toolgrid_preview_price | Credit estimate (no charge) |
| toolgrid_execute | Run a tool (same path as POST /v1/execute) |
| toolgrid_create_job | Async batch (jobs) |
| toolgrid_get_job | Job status for your account |
| toolgrid_balance | Remaining API credits |
Newly enabled gateway tools appear in search automatically — no separate MCP mapping. Cursor and ChatGPT debit the same API credit wallet.
5. Troubleshooting
| Symptom | What to do |
|---|---|
| 401 / invalid key | Create a new key on Keys |
| Subscription required | Activate Developer API on Dashboard |
| Insufficient credits | Buy API credits on Credits |
| Consent / sign-in loop | Sign in on www.toolgrid.io, then return to Approve on the consent page |
| Tools empty in ChatGPT | Start a new chat or reconnect the MCP app |
| Cursor cannot add URL MCP | Use ChatGPT OAuth path, or update Cursor to a build with remote MCP |
6. Security checklist
- Keep
tg_api_…in Cursor config / a password manager only — never in ChatGPT prompts, public repos, or gists. - Prefer OAuth for cloud AI clients.
- After demos: revoke OAuth grants on Dashboard → MCP; rotate test API keys if they left your machine.
- Only use HTTPS production endpoints for customer integrations.