# framework-mcp [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/81labsapps-ops/framework-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/framework-mcp

## Description
Verified, version-pinned Expo SDK docs for coding agents over remote MCP (Streamable HTTP).

## Tools
Capabilities this server exposes over MCP:

- **query_id**

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "framework-mcp": {
    "url": "http://localhost:3000/mcp"
  }
}
```

## Documentation

## What framework-mcp MCP server does

The framework-mcp MCP server provides coding agents with checked answers about framework and library versions that change faster than general model training data. Its initial coverage includes Expo SDK 54.0.0, Next.js 16.3.2, Supabase JavaScript client 2.112.3, Prisma ORM 7.9.1, Vercel AI SDK 7.0.77, and Nuxt 4.5.2.

Each covered framework has seeded question-and-answer entries based on official sources such as release notes, documentation, upgrade guides, and changelogs. The listed entries were verified on 2026-08-22. Coverage is version-specific, so an agent should identify the framework slug and version before requesting an answer.

## How it works

The framework-mcp MCP server uses the MCP SDK with Streamable HTTP transport. Connections are stateful and use one session per connection. An Express application handles requests, while Postgres stores the framework data and API-key records. Bearer authentication is enforced through the SDK middleware.

The available workflow is:

1. Call `list_frameworks` to see supported framework slugs, versions, and entry counts.
2. Call `query_framework_doc(framework, version, question)` to request a verified answer.
3. Keep the returned `query_id`.
4. Call `report_outcome(query_id, worked, note?)` to record whether the answer solved the problem.

A `ping(message)` tool is also provided for health checks. The repository documentation refers to three callable tool groups in one inspection example, while its tools section lists `ping`, `list_frameworks`, `query_framework_doc`, and `report_outcome`; verify the deployed endpoint with MCP Inspector if the exposed tool set matters to your client.

## Setup and configuration

Run the server locally with Node 24 and a Postgres database. The documented setup uses a Neon project and a development-branch connection string. Copy `.env.example` to `.env`, then set `DATABASE_URL` and `API_KEY_PEPPER`. The pepper should be a long random value.

Install dependencies, apply migrations, seed the database, and build the application with the repository's npm scripts. Create an API key with `npm run create-api-key -- "label"`; the raw key is displayed only once. Start development with `npm run dev`, then check `/health` on the local port.

For a remote deployment, the repository documents Railway for application hosting and Neon for Postgres. Production setup uses a separate database branch, `NODE_ENV=production`, and a generated `PUBLIC_HOSTNAME` so the SDK's host validation accepts real traffic. The MCP endpoint is `/mcp`, and clients send the key as `Authorization: Bearer <your-api-key>`.

## Tools and capabilities

- `list_frameworks`: returns covered frameworks, versions, and entry counts.
- `query_framework_doc`: asks a version-specific documentation question and returns a query identifier.
- `report_outcome`: records whether a returned answer worked, with an optional note.
- `ping`: performs a health check.
- Automatic seed loading supports adding framework JSON files under `db/seed/`.

The public service also documents self-service API-key creation by email, with one active key per email and IP-based rate limiting.

## Limitations and notes

The server does not provide unrestricted browsing of framework documentation. Answers are limited to the seeded entries and versions currently in its database. Adding coverage requires creating a correctly shaped seed file and rerunning the database seed command.

Billing, plan tiers, credit balances, per-key rate-limit enforcement, and feedback scoring are listed as deferred work rather than implemented features. API keys cannot be recovered after creation, so clients or operators must store them securely. The documented remote connection example targets Claude Code, while Cursor and other compatible MCP clients may require their own HTTP configuration format.

_Full upstream README: https://allmcps.com/mcp/framework-mcp/readme_