Neon + Grok Bot
Connect Neon to Grok Bot
Prepare a grounded database project inventory
Read projects with Grok Bot and Agent200. Prepare a database project inventory within the configured Neon account scope.
On this page
Overview
Identify the selected project and ask Grok Bot to use the Agent200 connection. Inspect tool activity so browser context or another app does not replace the requested read.
Start with one identified project. Preserve returned project, branch, database and operation fields; report missing data and keep the workflow read-only.
Provider reference: Neon API.
Use the provider credential described on the Neon parent page. Keep it in secure configuration and verify the selected tenant or account before reading.
- Connector
- Neon
- Works with
- Grok Bot ยท Agent app, through MCP
- Authentication
- Your Agent200 API key
- You need
- An Agent200 API key
- Tools
- 5 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- Neon enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- Grok Bot, with custom MCP servers allowed. Grok Bot comes with SuperGrok, Grok Business seats and paid Cursor plans. On a team, the admin's connector policy must allow the Agent200 server.
Connect Neon to Grok Bot
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Grok Bot in the next step, as "Authorization: Bearer <your key>". One key covers Neon and every other connector enabled for your project. Keep it out of chats and source control.
-
2
Step 2: Open the custom connector form
In Grok Bot, open Connect apps from the sidebar and choose Add a custom connector at the bottom.
-
3
Step 3: Fill in the server and your key
Enter the name Agent200, pick Type Remote HTTPS, enter the server URL and add one HTTP header:
Authorizationwith the valueBearerfollowed by your key. Leave Client ID empty, then choose Add plugin.Add a custom connectorMCP: Grok Bot custom connector form Name: Agent200 Type: Remote HTTPS Server URL: https://api.agent200.com/mcp/ HTTP headers: Authorization: Bearer YOUR_AGENT200_API_KEY -
4
Step 4: Attach Agent200 in a chat
In a Bot chat, type
@and attach Agent200 to the task. Custom servers are account-wide, so every Bot on the account can use it.
Test your connection
Run one request to check everything is wired up.
Ask
Read the Neon project I identify and prepare a database project inventory. Name the source and use only project, branch, database and operation fields. State access gaps; do not change records.
What should come back
- The selected project is identified.
- Only the returned project, branch, database and operation fields are reported.
- Access gaps and missing context are explicit; no source data is changed.
Check the selected project ID, account scope, read permission and pagination. A project inventory is control-plane metadata, not database row access. Do not expose connection strings or credentials in an agent answer.
Get your API key
Create a key in the Agent200 dashboard. It reaches Neon and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Neon to Grok Bot.
Goal: connect Neon to Grok Bot with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/neon/framework/grok-bot/ 1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Grok Bot's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure Neon is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to Grok Bot: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Grok Bot's exact menus or commands. 4. Check it works with this request: "Read the Neon project I identify and prepare a database project inventory. Name the source and use only project, branch, database and operation fields. State access gaps; do not change records." What should come back: - The selected project is identified. - Only the returned project, branch, database and operation fields are reported. - Access gaps and missing context are explicit; no source data is changed. 5. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/neon/framework/grok-bot.md
Neon tools Grok Bot can call
-
List projects
Readneon_list_projectsFind projects visible to the Neon API key.
-
Read a project
Readneon_get_projectRetrieve one project by ID.
-
List branches
Readneon_list_branchesFind branches for an identified project.
-
Read a branch
Readneon_get_branchRetrieve one branch by ID.
-
List databases
Readneon_list_databasesFind databases on the selected branch.
No tool matches that search.
How it works
-
01
You ask Grok Bot
In your own words, for something in Neon.
-
02
Grok Bot picks a tool
It sees the Neon tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
It reaches Neon with your Agent200 API key, within the endpoints your project allows.
-
04
Grok Bot answers
It gets the result back from the MCP server and uses it in its reply or its next step.
Permissions at every level. Your project settings decide which services and endpoints the agent may use.
Troubleshooting
The source cannot be read
Check the selected project ID, account scope, read permission and pagination. A project inventory is control-plane metadata, not database row access. Do not expose connection strings or credentials in an agent answer.
FAQ
How do I verify this result?
Compare the named project and returned project, branch, database and operation fields with the source. Treat missing information as missing, not as a fact.
