The Agent33 MCP connectors let you plug your own accounts — Basecamp, Sentral and IPONZ — into Claude (and ChatGPT) and drive them in plain language. This page is everything you need to connect, use and troubleshoot them.
MCP (the Model Context Protocol) is the open standard Claude uses to talk to outside tools. An MCP connector is a small secure service that exposes one of your systems — its projects, records, documents — as a set of actions Claude can call on your behalf. Add the connector once, and you can ask Claude to read and update that system in normal conversation.
Full two-way access to a Basecamp 3 account — projects, to-dos, message boards, card tables (kanban), docs & files, campfires, check-ins and webhooks. Ask Claude to triage a project, draft a message, or move a card.
Read access to a school's Sentral data — students, staff, classes, families, enrolments, attendance, welfare, timetables, reports and fees. Built read-only by design, given how sensitive student data is.
Access to the IPONZ register (New Zealand's Intellectual Property Office) — trade marks, designs and patents: case info, renewals, client/portfolio search, examiner tasks, discussions and documents. Optional write scope can pay renewals and file submissions.
Two ways to connect. The custom-connector method is easiest and needs no config files — use it unless you specifically need the manual route for Claude Desktop.
Works in Claude web and Claude Desktop. Claude handles the login for you.
https://basecamp-mcp.agent33.com/api/mcp and continue.Use this only if you need to wire the connector into Claude Desktop's config file directly. Requires Node.js.
https://basecamp-mcp.agent33.com/connect and approve access in Basecamp.bc-mcp:v1.…X-API-Key header (see below).// merge this into your existing config { "mcpServers": { "basecamp": { "command": "npx", "args": ["-y", "mcp-remote", "https://basecamp-mcp.agent33.com/api/mcp", "--header", "X-API-Key:bc-mcp:v1.<your key>"] } } }
Sentral has no third-party login, so instead of a login screen you provide three values from your school's Sentral instance. They're validated before a key is issued, then encrypted into that key.
Add the endpoint in Claude, then fill in the connector's own credential form.
https://mcp-sentral.vercel.app/api/mcp and continue.https://your-school.sentral.com.au, your X-API-KEY, and your X-API-TENANT (tenant ID).Same idea as Basecamp's manual method, with a Sentral-prefixed key.
https://mcp-sentral.vercel.app/connect and fill in the credential form.sentral-mcp:v1.…X-API-Key header, then quit with ⌘Q and reopen.{
"mcpServers": {
"sentral": {
"command": "npx",
"args": ["-y", "mcp-remote",
"https://mcp-sentral.vercel.app/api/mcp",
"--header", "X-API-Key:sentral-mcp:v1.<your key>"]
}
}
}
IPONZ (New Zealand's Intellectual Property Office) has no third-party login — every request is authenticated with subscription keys from your IPONZ account. The custom connector opens a short ToFU-branded credential form where you enter those keys once; they're validated against IPONZ, then encrypted into the connector key.
Add the endpoint in Claude, then fill in the connector's own credential form. Claude handles the OAuth handshake (Dynamic Client Registration + PKCE) for you.
https://mcp.tofumark.com/api/mcp and continue.Same idea as the others, with an IPONZ-prefixed key.
https://mcp.tofumark.com/connect and fill in the credential form.iponz-mcp:v1.…X-API-Key header, then quit with ⌘Q and reopen.{
"mcpServers": {
"iponz": {
"command": "npx",
"args": ["-y", "mcp-remote",
"https://mcp.tofumark.com/api/mcp",
"--header", "X-API-Key:iponz-mcp:v1.<your key>"]
}
}
}
No. The connectors are stateless and have no database. Your credential is encrypted (AES-256-GCM) directly into the key you use. Each request decrypts it in memory to talk to Basecamp, Sentral or IPONZ, then discards it. We never see your Basecamp password (that stays with Basecamp's own login), your Sentral or IPONZ keys are never stored, and we don't log secrets or the contents of your data.
Claude Desktop, Claude on the web, and ChatGPT all support custom MCP connectors and work with all three connectors. The custom-connector method (Method A) is the smoothest in Claude; the manual method (Method B) is there for Claude Desktop power users who prefer editing the config file.
Basecamp: revoke access from your Basecamp account under My profile → Apps with access. Once revoked, the key can no longer reach your account.
Sentral: delete the API key in Enterprise Setup → API Keys. That immediately invalidates any connector key built from it.
IPONZ: revoke or regenerate the subscription key in your IPONZ account. Revocation is handled by IPONZ, not by us — once a key is revoked, any connector key built from it stops working.
You can also just remove the connector inside Claude to stop using it.
Keys don't expire on their own. A Basecamp connector key stays valid until you revoke access in Basecamp or the server's encryption key is rotated. If a key ever stops working, just re-run the connect flow to issue a fresh one.
The most common cause is that the school's Sentral instance isn't reachable from the public internet over HTTPS. A localhost or private-network address can't be reached by the cloud connector.
Also confirm the three values are exactly right: the Base URL (no trailing path), the X-API-KEY, and the X-API-TENANT tenant ID. They're validated against Sentral at connect time, so a wrong value is rejected up front.
Both subscription keys are validated against IPONZ at connect time, so a rejection almost always means a key is wrong or doesn't have the right subscription. Confirm you've entered the IPONZ key (info / REST) and the IPONZ-Documents key in the right fields, and that they match the environment you picked — a Sandbox key won't work against Production, and vice-versa.
If iponz_task_list returns nothing, add your User Id (from your IPONZ web account); if portfolio search comes back empty, add your Customer/Agent Id. Run iponz_whoami to see what the connection currently knows about you.
Claude Desktop only reads the config on a full launch. Closing the window isn't enough — quit completely with ⌘Q on macOS (or right-click the tray icon → Quit on Windows), then reopen. The connector should appear on next start.
Yes. Both connectors are built to be deployed per-client with your own product name and domain — they already run for more than one organisation. If you'd like your own deployment, or a connector for a system that isn't listed here, get in touch.
Send a tools/list request to the MCP endpoint with your key as the X-API-Key header. A valid key returns the list of available tools.
curl -s https://basecamp-mcp.agent33.com/api/mcp \ -H "X-API-Key: bc-mcp:v1.<your key>" \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'