Presence Mcp

io.github.sara-star-quantPublished by GitHub account sara-star-quantv0.2.0Updated Oct 24, 2026

Read-only MCP access to presence: living project model and outcome telemetry.

Overview

AI-generated overview

Read-only MCP access to a local presence install's living project model and outcome telemetry for each repository.

What you can do
This PyPI launcher locates a local presence installation and forwards stdio to its MCP server. It exposes two read-only resources per repository: a living model.md in Markdown and recent commit, revert, and verification claims as a JSON array. The launcher itself speaks no MCP and is about 40 lines of stdlib-only Python.
When to use it
Use it when you already run the presence Claude Code plugin and want its project model and telemetry reachable from Claude Desktop, Cursor, Continue, or another MCP-aware client through a single command name instead of a machine-specific absolute path.
Requirements
Python 3.12 or newer and a local presence install (tested with 0.6.0 and later). The launcher resolves presence from the default plugin path or from the PRESENCE_MCP_CLI environment variable, and can use a different interpreter via PRESENCE_MCP_PYTHON. Linux and macOS are exercised in CI; Windows is untested.
Before you install
The server resolves the current repository from the launcher's working directory, so clients that start it from a fixed directory only see one repo; launch a separate instance per project or restart from the target project root. If PRESENCE_MCP_CLI is set to a missing path the launcher errors out rather than falling back. Resources are read-only.

Installation

In SourceWeft

  1. Open Presence Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

presence-mcp

[PyPI] [Python versions] [License: Apache 2.0] [CI] [MCP Registry]

PyPI launcher that exposes presence's living project model and outcome telemetry as MCP resources for Claude Desktop, Cursor, Continue, and other MCP-aware clients.

presence is a Claude Code plugin. It already ships a stdio MCP server at lib/cli.py mcp and exposes two read-only resources per repository (see What you get). This package is the PyPI shim that lets that server be listed in the official MCP Registry and invoked with a single command name in every per-client config, instead of an absolute path that varies per machine.

The launcher itself speaks no MCP. It locates a local presence install and forwards stdio to python lib/cli.py mcp. About 40 lines of Python, stdlib only.

Quick start

bash
pip install presence-mcp

Then point any MCP client at the presence-mcp command. For Claude Desktop, that's:

json
{  "mcpServers": {    "presence": {      "command": "presence-mcp"    }  }}

Full per-client config for Cursor and Continue below. Requires Python 3.12+ and a local presence install.

What you get

Two read-only MCP resources, one per repository you've worked on:

URIContentMIME type
presence://<repo_id>/modelLiving model.md (Markdown)text/markdown
presence://<repo_id>/telemetryRecent commit / revert / verification claims (JSON array)application/json

<repo_id> is a 12-char SHA-256 prefix of the repo. The server resolves the current repo from the launcher's working directory; see Working-directory caveat. Resource schema and protocol details: presence's docs/mcp.md.

Per-client configuration

The same presence-mcp command works in every client.

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json (macOS), or the equivalent on Windows / Linux:

json
{  "mcpServers": {    "presence": {      "command": "presence-mcp"    }  }}

Cursor

.cursor/mcp.json in the project root, or the global Cursor MCP settings:

json
{  "mcpServers": {    "presence": {      "command": "presence-mcp"    }  }}

Continue

~/.continue/config.json:

json
{  "mcpServers": [    {      "name": "presence",      "command": "presence-mcp"    }  ]}

Verify the install

The launcher accepts JSON-RPC on stdin. Pasting {"jsonrpc":"2.0","id":1,"method":"initialize"} and pressing Enter should yield an initialize response. You can also invoke it as python -m presence_mcp if a console script isn't convenient.

Environment variables

VariablePurpose
PRESENCE_MCP_CLIAbsolute path to presence's lib/cli.py. Overrides the default ~/.claude/plugins/presence/lib/cli.py lookup. If set but the path is missing, the launcher errors out instead of falling back, so typos surface.
PRESENCE_MCP_PYTHONPython interpreter to run presence with. Defaults to sys.executable of the launcher itself. Useful when presence is installed under a different Python (for example, a project venv).

If presence-mcp reports it could not locate presence, install presence at the standard Claude Code plugin path, or set PRESENCE_MCP_CLI.

Working-directory caveat

presence's MCP server resolves the current repo from the launcher's working directory via git rev-parse --show-toplevel. MCP clients that launch the server from a fixed directory will only see one repo. To switch repos, either launch a separate instance per project (set cwd in the client's per-server config), or restart the server from the target project root.

Compatibility

  • Python: 3.12 or newer. CI matrix covers 3.12 / 3.13 / 3.14.
  • presence: tested with >= 0.6.0. Older versions back to v0.4.1 (where the MCP server first shipped) may still work but are not exercised by CI.
  • Platforms: Linux and macOS exercised in CI. Windows is untested in v0.1.0. The launcher uses subprocess.run which is cross-platform, but the default presence install path (~/.claude/plugins/presence/lib/cli.py) needs a real Windows install to confirm. Report issues if you try it.

This launcher is protocol-agnostic: it does not rev when presence ships new MCP resources. It only revs when its own resolution logic, CLI surface, or server.json content changes.

Where to file issues

  • Launcher bugs (path detection, install errors, CLI argument forwarding): issues on this repo.
  • Resource-content bugs (what presence://*/model returns, telemetry schema, working-directory behavior, anything about the protocol itself): issues on the presence repo.

Disambiguation

presence's MCP server advertises serverInfo.name = "presence-mcp" in its initialize response. That's the server's MCP identity. This package is the PyPI launcher. The names match by intent.

Links

License

Apache-2.0. See LICENSE and NOTICE.

Source: README.md at commit c6854d8

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts