RMCP.DEV
← Registry

Developer Tools

projectstate.online

Manages project memory, status, tasks, decisions, and notes for AI-assisted development workflows.

1 endpoint5 known toolsFirst detected September 12, 2026Last detected September 12, 2026

ENDPOINT 1

https://projectstate.online/mcp

No auth detected

MCP server metadata

Name
projectstate
Version
0.2.1
Capabilities
experimentalpromptsresourcestools
Server instructions

projectstate keeps per-project memory for coding agents: decisions, attempts (what was tried and whether it worked), open tasks and notes, scoped to a project slug. Typical session: 1. project_open(project) at the start -> a short brief of status, open tasks, latest decisions and failures. 2. recall(project, query) before making a choice or repeating work -> the few most relevant entries, never the whole history. 3. remember(project, kind, title, body) whenever you decide something, try something, or finish/plan a task. 4. update(project, id, status=...) to close tasks, mark attempts, or supersede decisions. 5. project_status(project, set_status=...) to leave a one-line handoff note for the next session. Every call is metered (prices are listed per tool in tools/list _meta.priceUsd). Writes are idempotent.

Known tools 5

project_open

Open (or create) a project and get a compact brief: status line, open tasks, latest active decisions and failed attempts.

Potential side effects
project_status

Get the project's one-line status, open tasks and last change.

Inferred read-only
remember

Store one fact about the project.

Inferred read-only
recall

Search the project's memory with keywords and get the few most relevant entries (ranked, active entries first, superseded ones last), trimmed to `max_chars`.

Inferred read-only
update

Change an existing entry by id: set `status` (task open|done|dropped, attempt worked|failed|partial, decision active|superseded|reverted, note active|archived), replace `title`/`body`, `append` a line to the body (e.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.projectstate]
url = "https://projectstate.online/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "projectstate": {
      "type": "http",
      "url": "https://projectstate.online/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: projectstate
Remote MCP URL: https://projectstate.online/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "projectstate": {
      "url": "https://projectstate.online/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code 
{
  "servers": {
    "projectstate": {
      "type": "http",
      "url": "https://projectstate.online/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "projectstate",
  "transport": "streamable-http",
  "url": "https://projectstate.online/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.