Verified Agent Skill record

MCP Builder · MCP Use

Use this Skill to build, modify, debug, migrate, review, or verify TypeScript MCP servers and MCP Apps with mcp-use. It covers tools, resources, prompts, middleware, Views, authentication, Skills over MCP, scaffolding, and advanced features.

Tasks

Inspect the project’s package.json, server entry, exported tool references, mcp-env.d.ts, views/, skills/, and installed mcp-use version before changing code.
Build or modify TypeScript MCP server features such as tools, resources, prompts, middleware, Views, authentication, Skills over MCP, or advanced features using the installed mcp-use types and the relevant reference documentation.
For View-bound tools, define matching inputSchema and outputSchema values, return structuredContent in successful results, place the View at views/<name>/view.tsx, and export every statically declared tool reference consumed by the View.
Validate the smallest real lifecycle that demonstrates the changed behavior, expanding checks when types, package exports, authentication, or interactive behavior are affected.

Inputs

An existing TypeScript MCP project and its package.json, server entry, exported tool references, mcp-env.d.ts, views/, skills/, and installed mcp-use version.
A requested change involving MCP servers or MCP Apps, including tools, resources, prompts, middleware, Views, authentication, Skills over MCP, scaffolding, migration, or advanced features.
The installed mcp-use package, its exported types, generated declarations, and the project’s existing code.

Outputs

Modified or verified TypeScript MCP server or MCP App code that follows the installed mcp-use APIs.
MCP tool results using raw MCP result envelopes, including structuredContent when required and model-readable content for expected failures.
A verified implementation lifecycle appropriate to the changed behavior.

Limitations and checks

Do not invent exports, configuration fields, or callback shapes; confirm uncertain details in installed declarations or source.
Do not preserve APIs absent from the installed version solely because they appear in an existing project.
Do not return a plain domain object from a tool callback.
Do not bind a View without a matching outputSchema and structuredContent result.
Do not use module globals for cross-request identity, elicitation continuity, or durable business state.
Do not claim success from a source build alone when types, package exports, authentication, or interactive behavior changed.
Do not deploy or mutate external systems unless explicitly requested.
Confirm that the implementation uses APIs and callback shapes available in the installed mcp-use version.