Cretia
← Back to blog

How to connect Cretia to ChatGPT, Claude and other AI agents

By Montserrat Devars

Published

  • ChatGPT
  • Claude
  • Claude Code
  • Other MCP agents

Connect Cretia to ChatGPT, Claude or an MCP-compatible agent to work with your business from a conversation. Ask about services, invoices or quotes without copying records between apps. You choose what each connection can do and can revoke it from your profile.

You need a Cretia account with an active subscription and access to custom MCP connections in your AI app. Availability depends on its plan and workspace rules. If someone else manages the workspace, ask them to enable the connection.

The server URL is https://api.cretia.app/mcp. Use OAuth for ChatGPT and Claude: Cretia will ask you to sign in and review permissions. Never paste an API key into the conversation.

1. Connect ChatGPT

  • Open ChatGPT on the web. In Plugins, use + to add a custom MCP server. If your account shows Apps or Connectors instead, find the custom app creation option; developer mode or administrator access may be required.
  • Name it Cretia, enter https://api.cretia.app/mcp as the server URL and select OAuth.
  • If asked for a client identity, select CIMD, ChatGPT’s published identity. You do not need to register a client or make up a client secret for Cretia.
  • Continue to authorization. Sign in to Cretia, confirm the organization and choose permissions. Start with read-only access and enable only the modules you need.
  • Return to ChatGPT, finish creating or installing the connection and select it in a conversation with @Cretia. Try: “Use Cretia to show my services scheduled for today”.

Menu labels can change. Check the official custom MCP server guide and the developer mode and permission requirements if you cannot find the option.

2. Connect Claude

  • In Claude, open Customize → Connectors and add a custom connector. In a team workspace, an administrator may need to add it through organization settings first.
  • Name it Cretia and use https://api.cretia.app/mcp as the remote server URL.
  • Review the detected authentication, choose to sign in and select Claude’s published identity for OAuth. Avoid automatic client registration.
  • Sign in to Cretia, confirm your organization and grant the access you need. Read-only permissions are selected initially.
  • Return to Claude, enable Cretia in your conversation and ask: “Check Cretia and summarize my open quotes”.

If someone manages your workspace or you see different options, follow the Claude custom connector documentation.

3. Connect Claude Code

Add Cretia from your terminal with this command:

claude mcp add --transport http cretia https://api.cretia.app/mcp

Then open /mcp inside Claude Code, select Cretia and sign in. The same Cretia authorization page opens so you can choose an organization and permissions. Continue only if you started this connection on your computer.

4. Other MCP agents and scripts

If your client supports remote MCP over HTTP and custom headers, use an API key with limited permissions. Cretia OAuth currently accepts the published ChatGPT and Claude identities; other clients can use this alternative.

  • In Cretia, open Profile → Agents and API keys and create a new key.
  • Give it a name that identifies where you will use it and choose the minimum permissions. Start with read-only access.
  • Save the key when it appears: Cretia displays it only once.
  • Configure https://api.cretia.app/mcp as the HTTP server and add the header Authorization: Bearer YOUR_KEY in your client’s secure settings.

Keep the key out of prompts, screenshots and repositories. Apps without MCP support require an adapter; an API key alone does not add that capability.

What you can ask

  • “List my services scheduled for today and tell me which are still pending”.
  • “Show my outstanding invoices for this month”.
  • “Summarize my open quotes by customer”.

Results depend on the permissions and modules enabled for your connection. Customer accounts keep their company and location restrictions and do not gain access to the organization’s shared mailbox.

Permissions, expiry and revocation

A connection can never exceed your current Cretia access. Permission changes apply on its next request. Write permissions let an agent modify real data; email permission may allow it to send messages from a connected mailbox. Review each action before approving it.

To disconnect an app or key, open Profile → Agents and API keys and revoke its access. Its next request is blocked. API keys expire after one year and OAuth connections expire after 90 days without refreshing their tokens. Credential changes and account archival invalidate existing connections.

If the connection fails

Check that the URL ends in /mcp, your organization has an active subscription and your client permits custom connections. For OAuth, choose the provider’s published identity; do not choose unauthenticated access. If tools are missing, enable Cretia in the conversation or refresh the client’s tool list. Reconnect if access expired or was revoked.

You can add Cretia as a custom connection even if it is absent from your provider’s app directory. Read our privacy policy or contact support if you need help.

Simplify your business with Cretia

Invoicing, CRM, accounting and more. All in one platform.

Start for free