Connect an AI assistant

You can connect Congressio to an AI assistant and then just ask it things — "which papers are still missing a reviewer?", "open the call for papers", "how many people have registered?" — instead of clicking through the dashboard.

This works through the Model Context Protocol (MCP), an open standard for giving an assistant access to a tool. It is not Claude-specific: any assistant that supports MCP connectors can use it.

The address

https://www.congressio.net/api/mcp

That is all you need. There is no key to generate and nothing to paste — signing in happens through Congressio's own login and consent screen, the same way "Sign in with Google" works on other sites.

Adding it

Claude (web, desktop or mobile). Settings → Connectors → Add custom connector, paste the address, and leave the authentication options at their detected defaults. Claude will send you to Congressio to sign in and approve.

ChatGPT. Settings → Connectors → add a custom connector with the same address. Depending on your plan this may need to be done by a workspace admin.

Other assistants. Anything that accepts a remote MCP server URL — Le Chat, Cursor, VS Code and others — takes the same address.

If your assistant runs on your own machine and supports local servers instead, you can use the npm package:

{
  "mcpServers": {
    "congressio": {
      "command": "npx",
      "args": ["-y", "@congressio/mcp"],
      "env": { "CONGRESSIO_API_KEY": "cong_live_…" }
    }
  }
}

That route uses an API key from Organization settings → API rather than the sign-in flow.

Signing in

When you connect, Congressio asks you to sign in and then shows a consent screen listing exactly what the assistant will be able to do, and which of your organizations it will act in. A connector only ever gets access to the one organization you pick.

Two things worth knowing:

• If your account has two-factor authentication turned on, sign in with your password and authentication code. Social sign-in is deliberately refused for accounts with 2FA, because it would skip the second factor.
• The screen will say the application is not verified. That is expected and correct: assistants register themselves automatically, so Congressio has not vetted them. Check the name and the address it will return to before approving.

What it can see and do

An assistant is held to exactly the same permissions you have. It can never see or change something you could not see or change yourself in the dashboard, and everything it does is recorded against your name.

It can read the public conference directory, and — once you approve — your own conferences, submissions and attendee lists.

Whether it can also make changes depends on what your platform administrator has allowed for that connector. When writing is enabled, an assistant can create and publish conferences, open and close the call for papers, add and assign reviewers, register attendees, and release decisions.

Releasing decisions emails every author and cannot be undone, so an assistant has to confirm the exact number of people it is about to contact before anything is sent.

Disconnecting

Go to your profile page, find the application under connected applications, and disconnect it. Access stops immediately — both the assistant's current access and its ability to renew it. You can also remove the connector from the assistant's own settings.