Temp Notes MCP Server

Created By
landicefua year ago
Overview

What is Temp Notes MCP Server?

Temp Notes MCP Server is a Model Context Protocol (MCP) server designed to enable AI agents to store and retrieve temporary information across conversations and contexts, facilitating better state management and context preservation.

How to use Temp Notes MCP Server?

To use the Temp Notes MCP Server, integrate it into your MCP configuration using npx or install it via npm. You can then store, retrieve, and manage notes through a simple API.

Key features of Temp Notes MCP Server?

  • Persistent temporary storage across conversations
  • Simple API for reading, writing, and appending notes
  • Lightweight and easy to integrate with existing workflows
  • Enables complex multi-step tasks to be broken down into manageable pieces

Use cases of Temp Notes MCP Server?

  1. Managing complex coding tasks by storing checklists and progress.
  2. Preserving context across conversations to avoid losing information.
  3. Facilitating cross-repository information transfer for collaborative work.
  4. Supporting incremental documentation for projects.

FAQ from Temp Notes MCP Server?

  • Can I use Temp Notes MCP Server without installation?

Yes! You can use it directly with npx without needing to install it globally.

  • How does the note storage work?

Notes are stored in a designated file on your system, which is created automatically when you first write a note.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
landicefu
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Payai X402 Tools

2 hours ago
Payai X402 Tools

2 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago