state-server MCP Server

Created By
norisuke3a year ago
my new repository
Overview

what is MCP State Server?

MCP State Server is a TypeScript-based Model Context Protocol server that implements a simple notes system, demonstrating core MCP concepts through resources representing text notes with URIs and metadata.

how to use MCP State Server?

To use the MCP State Server, install the dependencies, build the server, and configure it with Claude Desktop by adding the server config to the appropriate directory based on your operating system.

key features of MCP State Server?

  • Resources representing text notes with URIs and metadata.
  • Tools for creating new notes with required parameters.
  • Prompts for generating summaries of all stored notes.

use cases of MCP State Server?

  1. Creating and managing text notes for various applications.
  2. Summarizing notes for quick reference.
  3. Integrating with other applications that support MCP.

FAQ from MCP State Server?

  • What is the purpose of the MCP State Server?

The MCP State Server is designed to manage and summarize text notes using the Model Context Protocol.

  • How do I install the MCP State Server?

You can install it by running npm install and then build it using npm run build.

  • Can I use it with other applications?

Yes! It can be integrated with applications that support the Model Context Protocol.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
norisuke3
Star
0
Language
JavaScript
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