Contact-Ops MCP Server

by unicorncommander Your server? Claim it

answering

Contact-Ops is answering right now. Last checked 9 min ago.

People, organizations, and relationships. Authenticated; OAuth 2.1 via Keycloak.

Uptime history 23 hours of history

23 hours agonow

100.0%

Uptime 24h

85 of 85 checks

—

Tools

hidden behind auth

437 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Contact-Ops every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add contact-ops --transport http https://mcp.contacts.unicorncommander.ai/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.contacts.unicorncommander.ai/mcp

~/.codex/config.toml

[mcp_servers.contact-ops]
url = "https://mcp.contacts.unicorncommander.ai/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "contact-ops": {
      "url": "https://mcp.contacts.unicorncommander.ai/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "contact-ops": {
      "type": "http",
      "url": "https://mcp.contacts.unicorncommander.ai/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.contacts.unicorncommander.ai/mcp	streamable-http	sign-in	391 ms	9 min ago

Alternatives to Contact-Ops

same job, measured the same way

Customer-Ops

by unicorncommander

Relationships and the 360 view. Authenticated; OAuth 2.1 via Keycloak.

answering

Meeting-Ops

by unicorncommander

Transcripts, recaps, and action items. Authenticated; OAuth 2.1 via Keycloak.

answering

Project-Ops

by unicorncommander

Tasks, boards, and time for a workspace. Authenticated; OAuth 2.1 via Keycloak.

answering

Tax-Planning-Ops

by unicorncommander

Tax scenarios, quarterlies, and memos. Authenticated; OAuth 2.1 via Keycloak.

answering

Accounting-Ops

by unicorncommander

Journal, invoices, and payment proposals. Authenticated; OAuth 2.1 via Keycloak.

answering

Email-Ops

by unicorncommander

Mailbox threads; drafts wait for a person. Authenticated; OAuth 2.1 via Keycloak.

answering

Libers Suite

by libers

Website analyses and Knowledge Packs for the authenticated account via OAuth 2.1 + DCR.

answering

Glue Up MCP by usefulapi

by usefulapi

Read Glue Up events, memberships, contacts, organizations and finance records.

13 tools answering

Contact-Ops — questions

Answers built from our own checks of this server.

Why is there no tool list for Contact-Ops?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Contact-Ops working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 85 of 85 checks got a reply (100.0%), average response time 437 ms. The bar chart above shows every period we have measured.

How do I connect Contact-Ops?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to Contact-Ops?

No API key is involved. Contact-Ops answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is Contact-Ops?

It answers our handshake in 437 ms on average, which is faster than 29% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.