Connect Claude or ChatGPT to InfoLobby
InfoLobby runs a remote MCP server at https://infolobby.com/mcp. Add it as a
connector in Claude or ChatGPT and the assistant can work with your real data —
find records, answer questions across tables, create and update rows, read and
post comments, handle attachments.
You do not paste an API key. You click Connect, sign in to InfoLobby, choose which workspaces to share, and approve. Access is revocable from your account settings at any time.
Connect from Claude
Claude on the web, desktop, and mobile all use the same connector.
- Open Settings → Connectors.
- Click Add custom connector.
- Paste the URL:
https://infolobby.com/mcp - Click Add, then Connect.
- Sign in to InfoLobby if you are not already, pick the workspaces to share, and click Authorize.
Claude will show InfoLobby's tools in the connector list once it is connected.
Connect from ChatGPT
- Open Settings → Connectors.
- Choose to add a custom connector (on some plans this lives under Advanced → Developer mode).
- Paste the URL:
https://infolobby.com/mcp - Approve the sign-in and workspace selection when prompted.
Connector availability differs by ChatGPT plan. If you do not see the option to add a custom connector, your plan or your workspace admin's settings do not allow it yet.
What the assistant can do
| Area | Actions |
|---|---|
| Discovery | List workspaces, list tables, read a table's field schema, list saved views |
| Records | Query with filters and sorting, read, create, update, delete |
| Comments | Read a record's thread, post a comment |
| Attachments | Upload, download, remove files on a record |
| Automations | List, read, validate and create flows — account owners only, and new flows start switched off |
The connection acts as you. It can only reach data you can already reach, and your workspace roles and field permissions apply unchanged. It cannot create or restructure workspaces and tables, manage members, or touch billing.
Two things are worth knowing before you start:
- Comments are visible to your team. A comment the assistant posts looks like a comment from you. Read them before you approve.
- Deletes are real. There is no undo on a deleted record, so confirm before telling an assistant to remove anything.
Using the command line instead
If you are working in Claude Code, Cursor, Gemini CLI, Codex or another local agent, do not use this connector — install the InfoLobby Skill instead.
The reason is context. An MCP server's tool definitions sit in the model's context window on every single turn, whether or not any tool gets used. A skill costs about a hundred tokens until the moment it is actually needed, then loads on demand. Local agents already have unrestricted network access, so the skill does everything the connector does for a fraction of the overhead.
The connector exists for Claude on the web and ChatGPT specifically, because their sandboxes cannot make the outbound calls a skill relies on.
Reviewing and revoking access
Go to Account → Connected Apps. Every authorization is listed with the app's name, whether it has write access, which workspaces it can see, and when it was last used. Revoke takes effect immediately and cannot be undone — the app has to be authorized again from scratch.
Revoking is also the right move if you are unsure about an app. Nothing is lost except the connection itself.
Troubleshooting
"Couldn't connect" straight away. Check the URL is exactly
https://infolobby.com/mcp with no trailing slash or path.
Sign-in loops back to the authorize screen. Your browser is blocking the session cookie. Try without an incognito window or a strict tracking blocker.
The assistant says a workspace does not exist. It was probably not ticked when you authorized. Revoke the app under Account → Connected Apps and connect again, selecting the workspace you need.
"API is disabled for this account". API access is switched off account-wide. An account owner can re-enable it.
Writes fail but reads work. The authorization was granted read-only. Revoke and re-authorize.
For developers
The server speaks MCP over Streamable HTTP with OAuth 2.1 (PKCE, dynamic client registration). Discovery documents:
https://infolobby.com/.well-known/oauth-protected-resourcehttps://infolobby.com/.well-known/oauth-authorization-server
Existing InfoLobby API keys (il_live_…, il_user_…) also work as bearer tokens
against /mcp, which is useful for scripted clients that cannot do an OAuth flow.
Every tool maps onto a documented public API endpoint and inherits
that endpoint's permissions and rate limits.