Join the waitlist to take part in the alpha.

Integrations

Plugged into what you already use.

Standards speaks MCP. Any remote MCP server connects from your settings, with no development work. Mailboxes and calendars get a native connector.

67 connections available today out of 160 listed.

The MCP server list that actually answers

Every server on this list was queried, not copied from a directory. The address, the authentication mode and, when the server is open, the tools it declares: all of it comes from its own response, recorded on 9 August 2026.

The best MCP servers, in the strict sense

Best does not mean favourite. These are the ones that connect today without OAuth, so in two minutes, and whose tool list we could read. The rest are waiting on OAuth support.

160 results

Integrations with no key or an API key connect in two minutes. The OAuth ones are waiting on the next release: the OAuth engine already runs for mailboxes, it remains to open it to MCP.

The other way

And Standards inside your tools.

Your workspace exposes its own MCP server, a REST API and a CLI. Your business objects become readable by any agent, under your roles and permissions.

  • Claude Code, Cursor, Codex

    MCP

    Your records, documents and searches become tools in the editor, under the same permissions as your users.

  • REST API

    API

    Every schema object generates its routes. Scoped API keys, revocable, per person or per workspace.

  • standards CLI

    CLI

    Records, schema, documents, keys and connectors from the command line. JSON, table or CSV output.