OpenAI / ChatGPT MCP documentation
Your legal workspace,
connected to ChatGPT.
Research case law and statutes with source links. Find your Gotham matters, documents and workflows. Prepare changes that you review and approve in Gotham.
Gotham Inc · Updated
https://api.trygotham.io/mcpThis guide is public and needs no sign-in. The connection requires a Gotham account. Use the connection made available to your ChatGPT account or an authorized custom connection. This page does not indicate directory approval or publication.
Connect your account
You need a verified Gotham account and accepted membership in the intended workspace. Its owner or admin must allow ChatGPT access. Your existing resource permissions, ethical walls and applicable workspace credits still apply.
- Open ChatGPT Plugins and use the Gotham connection available to your account. For an authorized custom test, select Add custom MCP server, use the name Gotham Legal AI and enter the server URL above.
- Select OAuth authentication and follow ChatGPT’s connection flow. Review its connection notice and the tools it discovers. Account and organization policies may restrict custom connections.
- Sign in using your existing Gotham account. Review the account and requested scopes, then select Allow on Gotham’s consent page and return to ChatGPT.
- In Gotham, an owner or admin opens the intended workspace’s Settings → Integrations → ChatGPT and enables Allow ChatGPT in this workspace.
- Start a conversation with Gotham enabled. Where supported, type @ and select the Gotham plugin. Ask ChatGPT to list your accessible workspaces.
For client-specific screens, read the official OpenAI connection guide. Labels and access can vary by client and organization.
Choose what ChatGPT can access
ChatGPT receives its own scoped connection. Tools check your current membership, consent, resource permissions and the selected workspace’s ChatGPT setting. Enabling Claude does not enable ChatGPT.
| Scope | What it allows |
|---|---|
gotham:read | Discover accessible workspaces and read supported research and workspace records. |
gotham:write | Prepare supported changes for approval. It does not replace your approval of each request. |
offline_access | Refresh the connection while its linked Gotham session remains valid, until disconnection or revocation. |
If consent lists only read access, the connection cannot prepare changes. Reconnect with a request that explicitly includes write permission when you need it.
Signing out of the Gotham session that authorized the connection, or letting that session expire, stops later calls and refresh. Sign in and reconnect to restore access. To revoke access, use your Gotham connected applications. Revocation does not delete records already created.
Ask in ordinary language
Use workspace and record names from Gotham. ChatGPT resolves internal references with list and detail tools. You should not have to find or paste UUIDs. Replace these fictional names with yours.
Research with sources
In my Research workspace, find Indian authorities about limitation for a contract claim. Include source links and explain any coverage gaps.
Find your work
Find the Acme acquisition matter in my Corporate workspace and show its status and due dates.
Prepare a change
Prepare an empty draft playbook called Supplier NDA review in my Corporate workspace.
Duplicate names need clarification. A paginated or incomplete list is not proof that a record is absent. Name the workspace explicitly: changing the workspace in your Gotham browser does not change the connection’s default home workspace.
Legal search uses Indian law by default, with US and UK sources when requested. Coverage can be incomplete. Read the linked authorities and have a qualified professional check legal output.
Tool reference
Both connections expose 18 tools: 12 for reading and status, and six for preparing changes. Results are bounded; list responses may include a cursor for more pages.
| Tool | Purpose |
|---|---|
list_workspaces | Resolve a workspace name to accessible workspaces enabled for this client. |
list_documents | Find accessible files by filename or query. Returns metadata and readiness, not full document contents. |
search_legal_sources | Search supported case law and legislation, with snippets, source links and coverage information. |
list_matters | Find accessible matters, their references, statuses and due dates. |
get_matter | Read matter details and the current revision before preparing a rename. |
list_workflows | Find accessible workflows and their published versions. |
get_workflow | Inspect workflow versions, published steps and required inputs. |
list_playbooks | Find accessible playbooks, their status and rule counts. |
get_playbook | Read accessible playbook versions, rules and source references. |
list_tabular_reviews | Find document review grids, their status and document counts. |
get_tabular_review | Read review columns and a page of document rows and answers. |
get_gotham_write_status | Check a prepared request’s decision, execution outcome and, for workflows, current run state. |
| Tool | What approval executes |
|---|---|
prepare_create_matter | Prepare a new matter with its proposed title, kind and jurisdiction. |
prepare_update_matter_title | Prepare a rename that executes only if the matter’s current revision still matches. |
prepare_save_search | Prepare a saved legal research query and label. |
prepare_run_workflow | Prepare a run of the current published workflow version. Execution uses workspace credits and may continue after approval. |
prepare_create_playbook | Prepare an empty draft playbook. Approval does not add rules or publish it. |
prepare_create_tabular_review | Prepare a review with selected documents and questions. Approval creates the review without starting analysis. |
Review, approve, then check the result
- Ask ChatGPT to prepare the change. It stores the exact proposal and returns a summary and a Gotham approval link.
- Open the link as the same Gotham user who connected ChatGPT. Read the workspace, proposed inputs and any credit notice.
- Select Approve or Decline on the Gotham page within the request’s ten-minute lifetime. A chat message does not approve it. An expired request needs a fresh proposal and link.
- Check the outcome with
get_gotham_write_status. A workflow’s creation receipt is separate from its current execution state.
Workflow runs use workspace credits. A draft playbook starts empty. Creating a tabular review does not start its analysis. Approval executes the stored proposal once and rechecks access and current resource state.
After you approve
On ChatGPT clients that support MCP events, ask to resume after approval or workflow completion. The client must establish a subscription first. Delivery depends on client support and an active subscription. If automatic continuation is unavailable, return to the same conversation and ask ChatGPT to check the request’s status.
Check the status of the request I just approved.
The client cannot approve on your behalf. Notifications report that something changed; they do not grant permission or prove that execution succeeded.
Data and privacy
Gotham receives the tool inputs ChatGPT sends for your request, such as research queries, workspace references, selected document references and proposed titles. Tool results return to ChatGPT for your conversation. Accessible records can contain personal or confidential data.
Prepared requests store the proposed change and its outcome. Tool-call audit records contain operational metadata rather than full tool arguments or results. Decided requests and connector audit metadata are retained for up to 13 months. Undecided requests are removed seven days after expiry. Created records follow the applicable workspace retention policy.
Your main Gotham session cookie is not sent to ChatGPT; the client receives its own scoped token. The connection does not collect the rest of your conversation as a separate conversation history. A skill uses the declared Gotham connector rather than sending your data to an additional service of its own.
Product processing, subprocessors, account retention and deletion rights are explained in the Gotham privacy policy. Your agreement and settings with OpenAI govern that provider’s handling of the conversation and returned data. The service is intended for users aged 18 or older.
Troubleshooting
Connected, but no workspace appears
Confirm the connected Gotham account, accepted workspace membership and the workspace’s ChatGPT setting. Ask an owner or admin to enable the intended workspace. The other client’s setting is separate.
The connection or consent expired
Start a fresh connection from ChatGPT. Sign in to Gotham if needed and complete the new consent flow. Do not reuse an old consent or callback URL.
A change needs write permission
Reconnect through a consent request that includes gotham:write. Read access cannot prepare changes. Write permission still requires you to approve each stored proposal in Gotham.
The approval page is expired or unavailable
Ask for a new proposal and use its new link within ten minutes. Open it using the same connected Gotham account. Already handled requests cannot be approved again; changed resources may require a new proposal.
The assistant asks for an ID or picks the wrong record
Provide the workspace and record name. Ask it to call the relevant list tool first and inspect further pages if needed. Clarify duplicate names using visible details; do not substitute an unrelated record.
Search is waking or coverage is incomplete
Follow returned retry guidance. A degraded response is not proof that no authority exists. Read linked sources and verify the legal proposition independently.
The conversation did not resume after approval
On ChatGPT clients that support MCP events, ask to resume after approval or workflow completion. The client must establish a subscription first. Delivery depends on client support and an active subscription. If automatic continuation is unavailable, return to the same conversation and ask ChatGPT to check the request’s status. Ask it to check the stored request, then the workflow’s current run state if applicable.
OpenAI’s review scanner asks me to reconnect
Scanner authorization is separate from your Gotham password and reviewer credentials. Reconnect the account in the plugin editor, complete fresh OAuth consent, and rescan. If the finding persists, record the failed scan ID, time and visible error for support. A cached “Authorized” label or an earlier result does not prove the latest scan succeeded.
The connection stopped after signing out
Sign in to Gotham and reconnect from ChatGPT. A new browser session alone does not revive a connection tied to an ended session.
A request is blocked by credits or permissions
The connection follows existing Gotham access and usage rules. Review the returned error, confirm the intended workspace, and ask its admin about access or available credits. A connection does not upgrade your plan or bypass a resource restriction.
Technical connection details
Remote MCP over HTTPS using Streamable HTTP, OAuth 2.0 and S256 PKCE. Anonymous tool access is refused. Opening the endpoint in a browser is not a tool connection test. No local executable or shared workspace password is needed.
- MCP endpoint
https://api.trygotham.io/mcp- Resource discovery
- OAuth protected-resource metadata
- Authorization discovery
- OAuth authorization-server metadata
- Manage access
- Gotham connected applications
Keep tokens, authorization callback URLs and approval links private. Use the endpoint for the client described on this page; the two connections have separate authorization and workspace controls.
Support from Gotham Inc
Email support@trygotham.io with the client, tool name, approximate time and visible error. Say whether it happened during connection, discovery, approval or execution. Use a synthetic example where possible. Do not send passwords, tokens, callback URLs or confidential documents.
Contact Gotham · Privacy policy · Terms of service
Back to top ↑