Productivity
usepromise.ai
An MCP server for Promise that helps users track commitments, follow-ups, and waiting-on items by surfacing what needs attention and evidence behind remembered follow-ups.
ENDPOINT 1
https://mcp.usepromise.ai/mcp
MCP server metadata
- Name
- Promise MCP
- Version
- 0.1.0
Known tools 11
connect_promiseReturn a Promise signup URL for users who want agent access to follow-up memory.
Inferred read-onlyCONNECT 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.promise-mcp]
url = "https://mcp.usepromise.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"promise-mcp": {
"type": "http",
"url": "https://mcp.usepromise.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: promise-mcp
Remote MCP URL: https://mcp.usepromise.ai/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": {
"promise-mcp": {
"url": "https://mcp.usepromise.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"promise-mcp": {
"type": "http",
"url": "https://mcp.usepromise.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "promise-mcp",
"transport": "streamable-http",
"url": "https://mcp.usepromise.ai/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.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.