Linkame MCP Server

by ohdonpiano Your server? Claim it

answering

Linkame is answering right now. Last checked 9 min ago. It exposes 25 tools.

Access authorized Linkame contacts, profiles, events, tickets and matching results.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 16 days of history

16 days agonow

100.0%

Uptime 24h

182 of 182 checks

Tools

read from the server

205 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 15

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 23 October 2026. No other catalogue keeps this.

23 Oct 12 tools appeared contacts.add_note, organizer.events.get_dashboard, organizer.events.get_matching_status and 9 more

23 Oct a tool changed version3 times that day

and 2 more, back to 23 October 2026

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

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 linkame --transport http https://linkame-a5883.web.app/mcp

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

https://linkame-a5883.web.app/mcp

~/.codex/config.toml

[mcp_servers.linkame]
url = "https://linkame-a5883.web.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "linkame": {
      "url": "https://linkame-a5883.web.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "linkame": {
      "type": "http",
      "url": "https://linkame-a5883.web.app/mcp"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 25

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

organizer

organizer.events.get_dashboard

Restituisce il riepilogo operativo aggiornato di un evento gestito.

organizer.events.get_matching_status

Restituisce configurazione, stato e conteggi del matching di un evento gestito.

organizer.events.get_registrations

Elenca le registrazioni paginando i partecipanti di un evento gestito.

organizer.events.get_sessions

Restituisce agenda, capienza e prenotazioni sessione di un evento gestito.

organizer.events.get_support_ticket

Restituisce un ticket di supporto dell’evento e la conversazione.

organizer.events.get_support_tickets

Elenca i ticket di supporto dell’evento con filtro stato e paginazione.

organizer.events.get_ticketing_summary

Restituisce riepilogo ticket, quantità vendute, assegnazioni e check-in.

organizer.events.list_managed

Elenca gli eventi gestiti dall’organizzatore o dal super admin con stato e date.

organizer.events.reply_support_ticket

Risponde a un ticket di supporto con conferma e idempotency key.

organizer.events.update_support_ticket_status

Cambia lo stato di un ticket di supporto con conferma e idempotency key.

organizer.support_tickets.list_all

Elenca i ticket di supporto di qualsiasi evento; solo super admin.

events

events.get

Restituisce i dettagli di un evento pubblicato o gestito dall’utente.

events.get_matching_results

Restituisce i risultati dell’ultimo matching completato dell’utente.

events.get_matching_status

Restituisce lo stato dell’ultimo matching dell’utente, eventualmente filtrato per evento.

events.get_my_ticket

Restituisce un biglietto dell’utente. Il QR viene incluso solo se richiesto esplicitamente.

events.list

Elenca gli eventi pubblicati visibili all’utente. Supporta paginazione con limit e offset.

events.list_my_registrations

Elenca gli eventi ai quali l’utente risulta registrato. Supporta paginazione con limit e offset.

events.list_my_tickets

Elenca i biglietti posseduti o trasferiti all’utente senza esporre il QR. Supporta paginazione con limit e offset.

contacts

contacts.add_note

Aggiunge una nota a un contatto. Richiede conferma esplicita e una idempotency key.

contacts.get

Restituisce un contatto della rubrica usando il suo identificatore stabile.

contacts.get_timeline

Restituisce la timeline di un contatto della rubrica. Supporta paginazione con limit e offset.

contacts.list_groups

Restituisce i gruppi di contatti dell’utente, inclusi gli inviti pendenti.

contacts.search

Cerca nella rubrica dell’utente per nome, azienda, ruolo, email, tag o note. Supporta paginazione con limit e offset.

account

account.get_current_user

Restituisce il profilo base dell’utente autenticato.

profile

profile.get_me

Restituisce i profili Linkame dell’utente autenticato.

Endpoints

URL	Transport	State	Latency	Checked
https://linkame-a5883.web.app/mcp	streamable-http	answering	86 ms	9 min ago
https://linkame.events/mcp	streamable-http	answering	186 ms	9 min ago

Alternatives to Linkame

same job, measured the same way

Wayfront

by wayfronthq

Permission-aware access to Wayfront clients, orders, projects, billing, tickets, and more.

answering

InfoTech-CRM

by infotech-crm

Read-only access to InfoTech-CRM leads, contacts, customers, deals, tickets and activities.

answering

Figma

by mcparmory

Export files, access design data, manage projects, comments, and team assets

239 installs/wk local only

Avala

by avala-ai

Read Physical AI datasets, projects, fleet and quality data. Requires authorized Avala access.

answering

Less Annoying CRM MCP by usefulapi

by usefulapi

Read and write Less Annoying CRM contacts, notes, tasks, events, pipelines and groups.

23 tools answering

THE COOP

by thecoop

Search THE COOP's published iGaming articles, supplier profiles and events with source links.

17 tools answering

Vocci

by vocci

Read-only MCP access to authorized Vocci sessions, notes, files, and memory search.

answering

Mixpanel MCP

by mrfentmen

Query Mixpanel events, funnels, retention, cohorts, and user profiles.

82 installs/wk local only

Linkame — questions

Answers built from our own checks of this server.

What can Linkame do?

It exposes 25 tools, read directly from the server on our last check. Among them: account.get_current_user, contacts.add_note, contacts.get, contacts.get_timeline, contacts.list_groups, contacts.search and 19 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Linkame mostly used for?

Its tools cluster around organizer, events and contacts. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Linkame working right now?

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

Is Linkame still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect Linkame?

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.

Does Linkame need an API key?

No. Linkame completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 25 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Linkame?

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