# mcp-use - Doramagic AI Context Pack

> Purpose: pre-work context for the user's host AI. This pack does not prove that the project has been installed, run, or validated.

## Project

- canonical_name: `mcp-use/mcp-use`
- capability: The fullstack MCP framework to develop MCP Apps for ChatGPT / Claude & MCP Servers for AI Agents.
- expected_user_outcome: The fullstack MCP framework to develop MCP Apps for ChatGPT / Claude & MCP Servers for AI Agents.

## Operating Boundaries

- Do not claim that the project has been installed, run, called through an API, or used on local files unless separate evidence proves it.
- Project facts must come from repo evidence, Claim Graph, or explicit source references.
- When a capability is not verified, mark it as unverified instead of completing it as fact.
- publish_status: `publishable`
- blocking_gaps: none

---

## Doramagic Context Augmentation

The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints.

## Human Manual Outline

Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph.

Host AI hard rules:
- Do not treat page titles, section order, summaries, or importance values as factual project evidence.
- When explaining the Human Manual outline, state that it is only a reading route or salience signal.
- Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph.

- **Framework Overview and Architecture**: importance `high`
  - source_paths: README.md, libraries/typescript/package.json, libraries/python/pyproject.toml, libraries/typescript/packages/mcp-use/src/server/mcp-server.ts, libraries/python/mcp_use/server/server.py
- **Building MCP Servers and Widgets (MCP Apps)**: importance `high`
  - source_paths: libraries/typescript/packages/mcp-use/src/server/index.ts, libraries/typescript/packages/mcp-use/src/server/tools/tool-registration.ts, libraries/typescript/packages/mcp-use/src/server/resources/index.ts, libraries/typescript/packages/mcp-use/src/server/widgets/mount-widgets-dev.ts, libraries/typescript/packages/mcp-use/src/react/useWidget.ts
- **MCP Client, Agents, and LLM Adapters**: importance `high`
  - source_paths: libraries/typescript/packages/mcp-use/src/client.ts, libraries/typescript/packages/mcp-use/src/agents/mcp_agent.ts, libraries/typescript/packages/mcp-use/src/managers/server_manager.ts, libraries/typescript/packages/mcp-use/src/adapters/base.ts, libraries/python/mcp_use/client/client.py
- **Inspector, CLI, Authentication, and Deployment**: importance `high`
  - source_paths: libraries/typescript/packages/inspector/src/client/App.tsx, libraries/typescript/packages/inspector/src/server/server.ts, libraries/typescript/packages/cli/src/index.ts, libraries/typescript/packages/cli/src/commands/deploy.ts, libraries/typescript/packages/cli/src/commands/servers.ts

## Repo Inspection Evidence

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `385e9fca8cdd783b4d7f2d7539b2441ef3ce6f27`
- inspected_files: `README.md`, `docs/generate_docs.py`, `docs/docs.json`, `docs/README.md`, `docs/context7.json`, `docs/CLAUDE.md`, `docs/snippets/snippet-intro.mdx`, `docs/snippets/youtube-embed.mdx`, `docs/home/index.mdx`, `docs/home/templates.mdx`, `docs/home/mcp101.mdx`, `docs/inspector/cli.mdx`, `docs/inspector/rpc-logging.mdx`, `docs/inspector/command-palette.mdx`, `docs/inspector/index.mdx`, `docs/inspector/connection-settings.mdx`, `docs/inspector/changelog.mdx`, `docs/inspector/debugging-chatgpt-apps.mdx`, `docs/inspector/integration.mdx`, `docs/inspector/development.mdx`

Host AI hard rules:
- Without repo_clone_verified=true, do not claim that the source code has been read.
- Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts.
- Without quick_start_verified=true, do not claim that the Quick Start path has run successfully.

## Doramagic Pitfall Constraints

These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes.

### Constraint 1: Installation risk requires verification

- Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/mcp-use/mcp-use/issues/1727
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 2: Installation risk requires verification

- Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/mcp-use/mcp-use/issues/1726
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 3: Configuration risk requires verification

- Trigger: Project evidence flags a configuration risk. Review the linked source before relying on this workflow.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/mcp-use/mcp-use/issues/1724
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 4: Security or permission risk requires verification

- Trigger: Project evidence flags a security or permission risk. Review the linked source before relying on this workflow.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/mcp-use/mcp-use/issues/947
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 5: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: Example: Chart Library MCP for financial pattern analysis
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Example: Chart Library MCP for financial pattern analysis. Context: Observed when using python
- Why it matters: Developers may fail before the first successful local run: Example: Chart Library MCP for financial pattern analysis
- Evidence: failure_mode_cluster:github_issue | https://github.com/mcp-use/mcp-use/issues/1286
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 6: Installation risk requires verification

- Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/mcp-use/mcp-use/issues/1286
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 7: Configuration risk requires verification

- Trigger: Project evidence flags a configuration risk. Review the linked source before relying on this workflow.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: capability.host_targets | github_repo:956472076 | https://github.com/mcp-use/mcp-use
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 8: Configuration risk requires verification

- Trigger: Developers should check this configuration risk before relying on the project: @mcp-use/cli 3.5.0
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: @mcp-use/cli 3.5.0. Context: Source discussion did not expose a precise runtime context.
- Why it matters: Upgrade or migration may change expected behavior: @mcp-use/cli 3.5.0
- Evidence: failure_mode_cluster:github_release | https://github.com/mcp-use/mcp-use/releases/tag/%40mcp-use/cli%403.5.0
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 9: Configuration risk requires verification

- Trigger: Developers should check this configuration risk before relying on the project: Refactor HttpConnector and StdioConnector with per-connector configuration
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Refactor HttpConnector and StdioConnector with per-connector configuration. Context: Observed when using python, playwright
- Why it matters: Developers may misconfigure credentials, environment, or host setup: Refactor HttpConnector and StdioConnector with per-connector configuration
- Evidence: failure_mode_cluster:github_issue | https://github.com/mcp-use/mcp-use/issues/947
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 10: Configuration risk requires verification

- Trigger: Developers should check this configuration risk before relying on the project: mcp-use 1.32.0
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: mcp-use 1.32.0. Context: Source discussion did not expose a precise runtime context.
- Why it matters: Upgrade or migration may change expected behavior: mcp-use 1.32.0
- Evidence: failure_mode_cluster:github_release | https://github.com/mcp-use/mcp-use/releases/tag/mcp-use%401.32.0
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.
