Shared team memory for agents MCP Server

by textforagents Your server? Claim it

answering

Shared team memory for agents is answering right now. Last checked 3 min ago.

Shared project-scoped memory for agent teams: typed records, corroboration, handoff briefs.

Uptime history 6 days of history · worst day 97%

6 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

343 ms

Response time

average over 24h

authentication required

Access

streamable-http

Shared team memory for agents does not always answer

Over the last week it answered 99.4% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add shared-team-agent-memory --transport http https://textforagents.com/products/shared-team-agent-memory/

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

https://textforagents.com/products/shared-team-agent-memory/

~/.codex/config.toml

[mcp_servers.shared-team-agent-memory]
url = "https://textforagents.com/products/shared-team-agent-memory/"

.cursor/mcp.json

{
  "mcpServers": {
    "shared-team-agent-memory": {
      "url": "https://textforagents.com/products/shared-team-agent-memory/"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "shared-team-agent-memory": {
      "type": "http",
      "url": "https://textforagents.com/products/shared-team-agent-memory/"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://textforagents.com/products/shared-team-agent-memory/	streamable-http	needs auth	339 ms	3 min ago

Alternatives to Shared team memory for agents

same job, measured the same way

Evc Mesh MCP

by entire-vc

Tasks, comments, shared memory and handoffs for teams of people and AI agents, over MCP.

answering

Agent Memory OS

by yamantaka520

Local-first memory engine for AI-agent teams: team/project ACL, recall, and federated sync.

505 installs/wk local only

TeamShared

by xhad

Shared memory for coding agents. Stop re-explaining your codebase every session.

92 tools answering

OneLore

by onelore

Shared project context for AI agents and teams: docs, tasks, and messages that stay current.

answering

Korpus

by korpus

Shared memory for teams and their AI agents: Markdown concepts with typed links in shared bundles.

answering

Chip MCP

by chip-ai

Project memory, tasks and Telegram notifications for your coding agent. Chip account required.

27 tools answering

Memocore

by memocore

Cloud memory for AI agents and teams — save, search, recall.

answering

Bilg

by bilgai

Shared memory for coding agents and their teams: docs, epics, tasks and decisions over MCP.

answering

Shared team memory for agents — questions

Answers built from our own checks of this server.

Why is there no tool list for Shared team memory for agents?

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 Shared team memory for agents working right now?

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

How do I connect Shared team memory for agents?

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 will need your own credentials: it refuses anonymous clients.

Does Shared team memory for agents need an API key?

Yes. Every time we knock, Shared team memory for agents answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Shared team memory for agents?

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