M
mcp-use/mcp-use
Framework for MCP apps and servers
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"mcp-use-mcp-use": {
"command": "npx",
"args": ["-y", "create-mcp-use-app@latest"]
}
}
}Parsed from the README we fetched on 2026-11-06; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"mcp-use-mcp-use": {
"command": "npx",
"args": ["-y", "create-mcp-use-app@latest"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio mcp-use-mcp-use -- npx -y create-mcp-use-app@latest
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Source
- collected from the abordage/awesome-mcp list · type: MCP server
- Harvest history
- first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
- Score
- score 1,003 · 10 sources · mcp
- Install
npx -y create-mcp-use-app@latest
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx -y create-mcp-use-app@latest. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.
The TypeScript framework for MCP
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
Build, test, and ship MCP servers, ChatGPT plugins, Claude connectors
Fully Typed, native Views and MCP Apps support, built-in Inspector and first class Agent experience.
Documentation
· Inspector
· Examples
· Deploy
> [!NOTE]
> Migrating from v1? Give it to your agent:
> text
> Migrate this mcp-use project to v2 following
> https://docs.mcp-use.com/v2/typescript/server/migration
> Read the migration guide →
## Get started
### Start with your agent
text
Build an MCP server: https://mcp-use.com/prompt.md
Read the prompt →
### Start with code
bash
npx -y create-mcp-use-app@latest
Run npm run dev in the generated project · open http://localhost:3000/mcp/inspector
TS Docs
## Everything you need to ship MCP
Fully typed
Zod schemas flow from tools to structured results, View props, and tool calls.
Native Views
Bind React Views directly to tools and ship interactive apps without custom extension wiring.
Agent-first and headless
Scaffold, invoke, inspect, screenshot, and deploy through your agent.
Built-in debugging tools
Inspect tools and Views in the browser or headlessly through the CLI.
## Quickstart
The scaffold gives you the server, TypeScript configuration, development scripts, Inspector, and a React view pipeline. Start it once and the MCP endpoint also serves a client-ready landing page with its connection URL and setup instructions.
Replace its index.ts with a view-bound tool like this:
index.ts — Server entry file for tool definition and metadata
typescript
import { MCPServer } from "mcp-use";
import { z } from "zod";
const server = new MCPServer({
name: "weather-app",
title: "Weather App",
version: "1.0.0",
});
const weatherInput = z.object({
city: z.string().describe("City to look up"),
});
const weatherOutput = z.object({
city: z.string(),
temperature: z.number(),
conditions: z.string(),
});
export const getWeather = server.tool(
name: "get-weather",
title: "Get weather",
description: "Get the current weather for a city",
inputSchema: weatherInput,
outputSchema: weatherOutput,
view: { name: "weather-card" },
annotations: {
readOnlyHint: true,
destructiveHint: false,
openWorldHint: true,
},
},
async ({ city }) => {
const weather = {
city,
temperature: 22,
conditions: "Sunny",
};
return {
content: [
type: "text",
text: Weather in ${city}: ${weather.conditions}, ${weather.temperature}°C,
},
],
structuredContent: weather,
};
},
);
export default server;
Explore MCP server tools →
## Add Views to your tools
Create views/weather-card/view.tsx. The directory name matches view.name on the tool:
view.tsx — Return a view from your tools: React weather card
tsx
import { useCallTool, useToolContext } from "mcp-use/react";
export default function WeatherCard() {
const { status, toolOutput, toolInput } =
useToolContext ();
const refresh = useCallTool("get-weather");
if (status === "pending") {
return Checking the weather in {toolInput?.city ?? "your city"}… ;
if (status === "error") return Could not load the weather. ;
const weather = refresh.data?.structuredContent ?? toolOutput;
return (
{weather.city}
{weather.temperature}°C · {weather.conditions}
void refresh.callTool({ city: weather.city })}
{refresh.isPending ? "Refreshing…" : "Refresh"}
{refresh.error && {refresh.error.message} }
Fully Typed, native Views and MCP Apps support, built-in Inspector and first class Agent experience.
Documentation
· Inspector
· Examples
· Deploy
> [!NOTE]
> Migrating from v1? Give it to your agent:
> text
> Migrate this mcp-use project to v2 following
> https://docs.mcp-use.com/v2/typescript/server/migration
> Read the migration guide →
## Get started
### Start with your agent
text
Build an MCP server: https://mcp-use.com/prompt.md
Read the prompt →
### Start with code
bash
npx -y create-mcp-use-app@latest
Run npm run dev in the generated project · open http://localhost:3000/mcp/inspector
TS Docs
## Everything you need to ship MCP
Fully typed
Zod schemas flow from tools to structured results, View props, and tool calls.
Native Views
Bind React Views directly to tools and ship interactive apps without custom extension wiring.
Agent-first and headless
Scaffold, invoke, inspect, screenshot, and deploy through your agent.
Built-in debugging tools
Inspect tools and Views in the browser or headlessly through the CLI.
## Quickstart
The scaffold gives you the server, TypeScript configuration, development scripts, Inspector, and a React view pipeline. Start it once and the MCP endpoint also serves a client-ready landing page with its connection URL and setup instructions.
Replace its index.ts with a view-bound tool like this:
index.ts — Server entry file for tool definition and metadata
typescript
import { MCPServer } from "mcp-use";
import { z } from "zod";
const server = new MCPServer({
name: "weather-app",
title: "Weather App",
version: "1.0.0",
});
const weatherInput = z.object({
city: z.string().describe("City to look up"),
});
const weatherOutput = z.object({
city: z.string(),
temperature: z.number(),
conditions: z.string(),
});
export const getWeather = server.tool(
name: "get-weather",
title: "Get weather",
description: "Get the current weather for a city",
inputSchema: weatherInput,
outputSchema: weatherOutput,
view: { name: "weather-card" },
annotations: {
readOnlyHint: true,
destructiveHint: false,
openWorldHint: true,
},
},
async ({ city }) => {
const weather = {
city,
temperature: 22,
conditions: "Sunny",
};
return {
content: [
type: "text",
text: Weather in ${city}: ${weather.conditions}, ${weather.temperature}°C,
},
],
structuredContent: weather,
};
},
);
export default server;
Explore MCP server tools →
## Add Views to your tools
Create views/weather-card/view.tsx. The directory name matches view.name on the tool:
view.tsx — Return a view from your tools: React weather card
tsx
import { useCallTool, useToolContext } from "mcp-use/react";
export default function WeatherCard() {
const { status, toolOutput, toolInput } =
useToolContext ();
const refresh = useCallTool("get-weather");
if (status === "pending") {
return Checking the weather in {toolInput?.city ?? "your city"}… ;
if (status === "error") return Could not load the weather. ;
const weather = refresh.data?.structuredContent ?? toolOutput;
return (
{weather.city}
{weather.temperature}°C · {weather.conditions}
void refresh.callTool({ city: weather.city })}
{refresh.isPending ? "Refreshing…" : "Refresh"}
{refresh.error && {refresh.error.message} }
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/mcp-use-mcp-use/)
- Source
- awesome · https://github.com/mcp-use/mcp-use
- Browse by field
- MCP servers
- Listed by
- 10 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.