Vendorctxd
Connects overstdio, http

Our grade: 4 checks

Login Login optional
Upkeep Active · 2026-11
Known bugs 0 open
Connection stdio, http

Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.

Community rating

3.1 10 reviews
20% would trust it in production
  • 5 1
  • 4 1
  • 3 6
  • 2 2
  • 1 0

Trust in production

  • Trust it - 20%
  • With caveats - 50%
  • Wouldn't - 30%

40% would recommend this server

How reviewers scored it

  • Setup & docs 3.2
  • Auth experience 3.4
  • Reliability 3.1
  • Maintainer responsiveness 3.8

Why it got a C

An MIT-licensed Python tool: a tracker syncs only the folders you add into a local store (ctxfs), and the MCP tools can only read it (stat, list, tree, glob, read, read lines, grep), with bounded results. By default it runs on a private Unix socket with no token, and ctxd-mcp bridges that to stdio. Over TCP every request needs a bearer token, even on loopback, with separate read, submit, status and admin scopes that you can revoke, and serving beyond localhost needs --allow-network plus TLS. No advisories on record and commits land almost daily, nearly all from one maintainer. Biggest deduction: grep runs the ripgrep binary on a pattern the model writes (without a shell, and with a timeout), and the local default has no token, so any process running as your user can read everything you tracked.

How to connect

// ~/.cursor/mcp.json (after pip install ctxd)
{ "mcpServers": { "ctxd": { "command": "ctxd-mcp" } } }

Is ctxd MCP Server safe?

Is ctxd MCP Server safe to use?

ctxd MCP Server grades C (usable with care). Login is optional, so check that it is turned on in your setup. Upkeep is hard to verify (closed source or a single maintainer), so pin the version you tested. It shells out to helper programs or serves HTTP without enforced TLS, so keep it local and isolated.

Does ctxd MCP Server have known vulnerabilities?

Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.

Does ctxd MCP Server support authentication?

Optionally. It can run with a login, but it does not require one, so turn it on.

Embed this badge

Maintain this server? Add the grade to your README.

TrustedMCP grade C

Markdown

[![TrustedMCP grade C](https://trustedmcp.io/badge/ctxd.svg)](https://trustedmcp.io/servers/ctxd)

HTML

<a href="https://trustedmcp.io/servers/ctxd"><img src="https://trustedmcp.io/badge/ctxd.svg" alt="TrustedMCP grade C" height="80"></a>

Community reviews

Jack Wilson Platform engineer
Trusts with caveats Recommends

Handy for dev, careful in prod

Good for experimenting, still deciding about production. Auth is optional, which is convenient locally. I turned it on before sharing it with the team. Recommended, with sensible guardrails.

Used for Summarising meeting notes

  • Setup & docs 4/5
  • Auth experience 4/5
  • Reliability 2/5
  • Maintainer responsiveness 4/5
Hannah Larsen Software engineer, agency
Trusts with caveats

Would not run this unattended

Gave it a fair shot over two weeks. I run it with auth enabled. Without it I would not let it near anything shared. Fine in production if you sandbox it.

Used for Pulling up-to-date library docs into prompts

  • Setup & docs 3/5
  • Auth experience 3/5
  • Reliability 3/5
  • Maintainer responsiveness 2/5
Mateo Garcia Eng lead, fintech
Trusts with caveats Recommends

Good, but read the permissions first

Useful tool, though I would not hand it to a junior unsupervised. Narrowing the scopes took ten minutes and made me much happier running it. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent.

Used for Keeping a team knowledge base tidy

  • Setup & docs 3/5
  • Auth experience 3/5
  • Reliability 2/5
  • Maintainer responsiveness 4/5
Grace Park ML engineer
Trusts in production Recommends

Our team uses it every day

Started with it as an experiment, now it is a fixture. I run it with auth enabled. Without it I would not let it near anything shared. Releases come often and the changelog is clear.

Used for Answering questions from our internal wiki

  • Setup & docs 4/5
  • Auth experience 4/5
  • Reliability 4/5
  • Maintainer responsiveness 4/5
Felix Wagner Solo founder
Trusts in production Recommends

Exactly what I needed from ctxd

Installed it on a Friday, it was part of my workflow by Monday. Out of the box it runs without sign-in, so remember to enable auth before exposing it anywhere. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Good choice if you need ctxd in your agent.

Used for Answering questions from our internal wiki

  • Setup & docs 5/5
  • Auth experience 4/5
  • Reliability 5/5
  • Maintainer responsiveness 5/5
Noah Fischer Knowledge manager
Trusts with caveats

Mixed feelings after two weeks

It does the job, but it took some tweaking. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Out of the box it runs without sign-in, so remember to enable auth before exposing it anywhere.

Used for Drafting docs from existing pages

  • Setup & docs 3/5
  • Auth experience 3/5
  • Reliability 4/5
  • Maintainer responsiveness 5/5
Rosa Morales Backend engineer
Would not trust in production

Does the job, docs could be better

Took longer to configure than I expected. Auth is optional, which is convenient locally. I turned it on before sharing it with the team. Turned on read-only mode on day one, highly recommend doing the same. For anything real I would look elsewhere.

Used for Summarising meeting notes

  • Setup & docs 3/5
  • Auth experience 4/5
  • Reliability 2/5
  • Maintainer responsiveness 4/5
Ryan O'Connor Staff engineer
Would not trust in production

Works, just lock it down

Mostly reliable, with the odd timeout. Out of the box it runs without sign-in, so remember to enable auth before exposing it anywhere.

Used for Finding the right runbook during incidents

  • Setup & docs 2/5
  • Auth experience 4/5
  • Reliability 4/5
  • Maintainer responsiveness 4/5
Andre Dubois Developer, healthtech
Trusts with caveats

Solid core, fiddly setup

I like it, with reservations. Token setup is the fiddliest part, after that it is smooth. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. I would use it in prod, but only with a human approving writes.

Used for Finding the right runbook during incidents

  • Setup & docs 3/5
  • Auth experience 3/5
  • Reliability 4/5
  • Maintainer responsiveness 4/5
Leah Cohen Security engineer
Would not trust in production

Not ready for anything that matters

Not what I expected from the description. Used a fine-grained token with short expiry and it works fine with that. Not something I would put in production yet.

Used for Onboarding Q&A for new hires

  • Setup & docs 2/5
  • Auth experience 2/5
  • Reliability 1/5
  • Maintainer responsiveness 2/5

Write a review

Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.

How was it overall?

Would you trust it in production?
Would you recommend it to another team?

Score the details

Setup & docs
Auth experience
Reliability
Maintainer responsiveness

Tell other teams how it went

About you