Permissioned MCP Server
This server provides a minimal, permissioned note-taking system over MCP, supporting listing, reading, creating, and deleting notes with scope-based access control. Tools are hidden or rejected based on granted scopes.
List notes (
notes.list): Retrieve metadata for all notes (no bodies). Read-only and idempotent. Requiresnotes:readscope.Read a note (
notes.get): Get full content by UUID. Read-only and idempotent. Requiresnotes:readscope.Create a note (
notes.create): Add a note with a title (max 120 characters) and body (max 10,000 characters). Requiresnotes:writescope.Delete a note (
notes.delete): Permanently remove a note by UUID. Requiresnotes:adminscope (not exposed in schema by default). Destructive operations require a confirmation step.
Additional safety and persistence features: Unauthorized tools are omitted from discovery and rejected at execution; audit logs exclude sensitive content; notes are stored locally with atomic writes and restrictive file permissions.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Permissioned MCP Server list my notes"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Permissioned MCP Server
A compact Model Context Protocol server that demonstrates the parts usually missing from quickstarts: explicit tool boundaries, least-privilege discovery, execution-time authorization, destructive-action confirmation, and metadata-only audit logs.
The domain is deliberately boring: a local note store. The reference is about designing a safe boundary between an AI agent and real side effects.
What it demonstrates
JavaScript on Node.js with the official MCP SDK v2
Narrow read, write, and destructive tools
Separate
notes:read,notes:write, andnotes:adminscopesUnauthorized tools omitted from
tools/listand rejected again at executionIdentifier-bound confirmation for destructive actions
Structured tool results and MCP behavior annotations
Audit events that never log arguments, content, or credentials
Atomic local persistence with restrictive file permissions
Tests for policy, handlers, persistence, and failure cases
Related MCP server: mcp-hardened
Run it
Requires Node.js twenty or newer.
npm install
cp .env.example .env
MCP_SCOPES=notes:read,notes:write npm startExample client configuration:
{
"mcpServers": {
"permissioned-notes": {
"command": "node",
"args": ["/absolute/path/to/permissioned-mcp-server/src/server.js"],
"env": {
"MCP_SCOPES": "notes:read,notes:write",
"MCP_DATA_FILE": "/absolute/path/to/notes.json",
"MCP_ACTOR": "local-agent"
}
}
}
}Start read-only. Grant notes:write only when mutation is necessary. Keep notes:admin out of the default configuration.
Tool boundary
Tool | Scope | Side effect |
|
| Returns metadata only |
|
| Reads one note |
|
| Creates one note |
|
| Permanently deletes one note |
See the decision record for the reasoning behind discovery filtering, double authorization, confirmation design, audit redaction, transport choice, and storage isolation.
Verify it
npm run check
npm testThe test suite never starts a model or calls a paid API.
Production notes
This is a local stdio reference, not a turnkey hosted authorization server. Before exposing an MCP server over Streamable HTTP, add OAuth-based authorization, token audience validation, HTTPS, rate limits, tenant isolation, durable audit storage, and client-specific consent.
License
MIT
Built by Lanier, an applied AI studio. More free tools at lanierdev.com/tools.
Available Tools
3 toolsnotes.createA
Create a local note. Requires the notes:write scope.
Inputs: body (required), title (required).
notes.getARead-onlyIdempotent
Read one note by its opaque identifier.
Inputs: id (required).
notes.listARead-onlyIdempotent
List note metadata without returning note bodies.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: list returns metadata, get returns a full note, and create adds a new note. No overlap in functionality.
All tools follow the consistent pattern 'notes.<verb>', using simple, descriptive verbs (list, get, create). No naming style deviations.
Three tools is a reasonable scope for a basic note management server. It covers core operations without being too sparse or excessive.
The set supports listing, reading, and creating notes but lacks update and delete operations. While a minimal viable set, these missing operations are notable gaps for typical CRUD coverage.
Maintenance
Related MCP Connectors
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
The MCP server that vets MCP servers: identity, risk grade and per-tool risk before you install.
Related MCP Servers
- AlicenseCqualityDmaintenanceAn educational MCP server exposing shell command execution (PowerShell and sh) and a benign tool for learning about MCP tools, resources, and security risks like tool poisoning.33MIT
- AlicenseBqualityDmaintenanceA deliberately small MCP server that demonstrates security hardening against the OWASP MCP Top 10 with tools for file search, record queries, and document fetching, each defended against path traversal, SQL injection, and SSRF.4MIT
- FlicenseNot gradedqualityFmaintenanceA governed MCP server exposing 37 risk-checked tools with signed Ed25519 receipts on a Bitcoin-anchored ledger, failing closed if governance or receipt writing fails.-
- AlicenseNot gradedqualityDmaintenanceA least-privilege enforcement proxy for MCP servers. It sits between MCP clients and upstream servers, enforcing tool policies, hiding denied tools, requiring human approval for risky actions, and providing a structured audit trail.MIT