skills/mcp-use__mcp-use
1
0
Fork 0
mirror of https://github.com/mcp-use/mcp-use.git synced 2026-09-14 18:06:01 +08:00
Code Issues Packages Projects Releases Wiki Activity
1,620 Commits 360 Branches 1,651 Tags
codex/a2ui-example
Commit Graph

8 Commits

Author SHA1 Message Date
Andrew Khadder f2f4fdbf33 Canary (#2334) 
* fix(cli): drop the React plugin from the binding-validation server

That server is only created when a project has no views (build.ts calls it
under views.length === 0), so it never has JSX to transform. Loading
@vitejs/plugin-react there pulls react, react-dom and both jsx runtimes into
optimizeDeps, which cannot resolve them because such a project has no reason
to depend on React.

Result was four 'Failed to resolve dependency' lines on the first build of a
fresh scaffold, on 3 of the 4 templates.

react() had no other use in views.ts, so the import goes too.

Closes #2297

* fix(create-mcp-use-app): send "Learn more" to the mcp-use docs (#2328)

* fix(create-mcp-use-app): send "Learn more" to the mcp-use docs

The last line the scaffold prints is:

  📚 Learn more: https://manufact.com/docs

That URL no longer reaches mcp-use documentation. It redirects twice and
lands on Manufact's own dashboard docs:

  https://manufact.com/docs -> 200 https://docs.manufact.com/dashboard

So someone who has just created an mcp-use server is pointed at a
different product's dashboard guide. The README the same command writes
into the new project points at the mcp-use quickstart instead, so the two
halves of one tool disagree.

Point it at the quickstart, which resolves directly with no redirect:

  https://docs.mcp-use.com/v2/typescript/getting-started/quickstart -> 200, 0 hops

The feedback line below it still mentions manufact.com, which is correct:
that one is about where to reach the people, not the docs.

* fix(create-mcp-use-app): use the bare docs host in "Learn more"

Review feedback: docs.mcp-use.com already redirects to the getting-started
page, and the short host reads better in a console message than the full
path.

  https://docs.mcp-use.com -> 200 https://docs.mcp-use.com/v2/typescript/getting-started/welcome

* chore: enter canary prerelease mode

* chore(typescript): version packages (canary)

* test(agent): assert in the two tests that assert nothing (#2316)

Two tests in @mcp-use/agent run their subject and then check nothing, so
they pass no matter what the code does. Both say so in a trailing comment.

stream_events.test.ts "should clean up resources on completion" installs
a spy on agent.close(), consumes the stream, and never looks at the spy.

agent-telemetry.test.ts "should track error type on failure" swallows the
error and leaves a comment guessing that telemetry "might not be called".
It is called: the recorded execution carries success false and errorType
"execution_error".

Both assertions were checked in the failing direction against a
deliberately broken source, not just against a passing run:

  close() calls in the cleanup paths removed
    -> expected "close" to be called at least once

  errorType hardcoded to null
    -> expected { executionMethod: 'stream', … } to match
       object { success: false, errorType: 'execution_error' }

No new test files and no new cases. These are the same two tests, now
able to fail.

* fix(client): disconnect the session createSession replaces (#1964)

* chore(typescript): version packages (canary)

* docs(typescript): enforce the TypeDoc coverage gate the packages already declare (#2312)

* docs(typescript): enforce the TypeDoc coverage gate the packages already declare

Each package's typedoc.json sets validation.notDocumented and
treatWarningsAsErrors, and eslint.config.js states that documentation
coverage "is enforced against each package's public entrypoints by its
strict TypeDoc configuration".

It is not. The only invocation is `pnpm docs:api`, which runs typedoc
with the root typedoc.options.json in packages mode. Validation from the
sub-package configs is applied, but treatWarningsAsErrors is not, so the
command reported 15 coverage warnings and still exited 0.

Set treatWarningsAsErrors in the root options and clear what the gate
then catches:

- Document the members of SkillSnapshotEntry.resources, required by
  packages/server/CLAUDE.md and missing.
- Document the members of SkillsListResult, SkillGetResult,
  SkillDirectoryEntry and SkillDirectoryReadResult in the client.
- Drop five intentionallyNotDocumented entries for react.UseWidgetResult
  and react.UserAgent, neither of which exists in the server source any
  more, and the intentionallyNotExported entry for UseWidgetResultBase.
- Add TurbopackConfig to intentionallyNotExported, matching the existing
  NextHeaderRule entry for the same pattern in the same file, and
  FinishOAuthAuthorization on the client side.

`pnpm docs:api` now exits 0 with zero warnings, and exits 3 again if any
public export loses its documentation.

No changeset: the source edits are doc comments only, with no runtime or
type change to any published API.

* chore(typescript): ignore generated TypeDoc output in eslint

`.typedoc/` is gitignored but not eslint-ignored, so running
`pnpm docs:api` and then `pnpm lint` reports 534 errors from the
generated, minified theme assets. The other generated output
directories are already listed.

* docs(tunnel): bring the fourth package under the same coverage gate

server, client and agent each carry a typedoc.json with
validation.notDocumented and treatWarningsAsErrors. tunnel is in the same
root entryPoints list and had no config at all, so turning the gate on
would have left it as the one published package still unchecked.

Add the matching config and document the three inline members it turns
up, on TunnelManager.start and TunnelManager.status.

* ci(docs): run the documentation checks on canary (#2321)

The Documentation workflow regenerates the API reference, runs
`mint broken-links`, and fails if the committed docs are out of date. It
triggers on `main` and `monorepo`.

`monorepo` does not exist. `git ls-remote --heads origin monorepo` returns
nothing, so that half of the trigger has been dead for a while.

Meanwhile every published package's source lands on `canary` first, and
the workflow never runs there. Checked against the four most recent
canary-targeted pull requests, #2316, #2312, #2309 and #2307: the
"Generate and validate API documentation" check is absent from all of
them, while it runs on main-targeted PRs that touch the same paths.

The practical effect is that documentation drift and broken links are
only caught on the canary-to-main release PR, in one batch, rather than
on the change that introduced them.

Point the trigger at `canary` instead of the branch that is gone. The job
only reads: it regenerates into the working tree and fails if anything
differs. It publishes nothing, so running it on canary is safe.

* docs(cli): remove inaccurate binding server comment

* chore(typescript): version packages (canary)

* fix(inspector): warn when model tool limit is exceeded (#2333)

* chore(typescript): version packages (canary)

* docs: update canary changelogs

* fix: address canary review findings

---------

Co-authored-by: ayaangazali <ayaangazali.work@gmail.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Vihaan Agarwal <vihaan@clique.so>
 2026-08-26 12:17:49 -07:00
Andrew Khadder 33e30cb8e3 Canary (#2117) 
* fix(cli): report success from mcp-use typecheck (#2099)

`tsc --noEmit` prints nothing on a clean project, so `mcp-use typecheck`
exited 0 with no output at all, which is indistinguishable from the
command hanging or silently failing.

Print `[mcp-use] no type errors (<duration>ms)` on exit code 0, matching
the existing `[mcp-use] built ... (<duration>ms)` line from `build`.
Failing runs are untouched and still show only the compiler's own
diagnostics.

Closes #2083

* chore: enter canary prerelease mode

* chore(typescript): version packages (canary)

* chore: sync main into canary (#2119)

* chore(release): exit prerelease mode and publish npm README hotfix

Publishes mcp-use 2.0.1 and @mcp-use/inspector 20.0.1 with the repository README included in the mcp-use package tarball.

* chore(release): exit prerelease mode and publish npm README metadata hotfix

Publishes mcp-use 2.0.2 and @mcp-use/inspector 20.0.2 after preparing README metadata before npm publication.

* chore(release): exit prerelease mode and commit npm package README

Publishes mcp-use 2.0.3 and @mcp-use/inspector 20.0.3 with a committed package-root README.

* chore(release): exit prerelease mode and fix npm README assets

Fix npm README asset and repository links, publish mcp-use 2.0.4, and keep Inspector aligned at 20.0.4.

* Update libraries/typescript/packages/server/README.md

Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>
Signed-off-by: Andrew Khadder <54488379+khandrew1@users.noreply.github.com>

* docs: sync migration guide link

---------

Signed-off-by: Andrew Khadder <54488379+khandrew1@users.noreply.github.com>
Co-authored-by: Enrico Toniato <2827496+tonxxd@users.noreply.github.com>
Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>

* fix(cli): say whether `start` mounted the inspector (#2100)

* fix(cli): say whether start mounted the inspector

`mcp-use dev` advertises the inspector in its banner, but `mcp-use start`
says nothing about it and `${basePath}/inspector` 404s unless
`--with-inspector` was passed. With no hint, that reads as a broken
production build rather than an opt-in.

Plain `start` now prints that the inspector is not mounted and how to
mount it, and `--with-inspector` prints the URL it was mounted at, which
was previously silent too.

Closes #2084

* fix(cli): drop the inspector-not-mounted line from start

Per review: most people running start do not want the inspector, so
announcing its absence is noise. Plain start is now silent about the
inspector again, and only the --with-inspector path prints its URL.

Updates the spec, the changeset, and swaps the test to pin the silence
instead of the message.

* chore(typescript): version packages (canary)

* chore: upgrade changesets cli to 2.31.1 (#2121)

* fix(ci): pin pnpm in the docs workflow so the job can start (#2116)

The docs job fails in "Set up pnpm" before it generates anything:

  Error: No pnpm version is specified.

pnpm/action-setup@v4 was used with no version:, so it falls back to
reading packageManager from package_json_file, which defaults to the
repository root. This repo has no root package.json, so the step could
never succeed and the check was red on every branch including main.

Pins 11.13.1, matching all nine action-setup uses in ci.yml and the
packageManager field in libraries/typescript/package.json.

* fix(cli): support package-manager dev arg forwarding (#2124)

* fix(cli): support package-manager dev arg forwarding (MCP-2549)

* chore: add MCP-2549 changeset

* fix(cli): normalize forwarded arguments across commands

* chore(typescript): version packages (canary)

* docs: fix TypeScript README links into the removed mcp-use package (#2114)

The v2 merge deleted libraries/typescript/packages/mcp-use, but the
TypeScript README still pointed at it in four places: the three logo
sources at the top of the page, and the documentation link at the bottom.

The logo now uses the absolute raw.githubusercontent.com URL that every
sibling package README already uses, and the docs link points at
packages/server, which is where the mcp-use package lives in v2 and what
the create-mcp-use-app and inspector READMEs already link to.

* fix(create-mcp-use-app): drop stale main field and give templates distinct descriptions (#2085)

* fix(create-mcp-use-app): drop stale main field and give templates distinct descriptions

Two small things in the scaffolded package.json, both visible as soon as
you generate a project.

main pointed at dist/index.js. v2 builds emit .mcp-use/build instead, so
that path never exists and main never resolves. These templates are apps
you run with mcp-use start, not packages anyone imports, and .mcp-use is
gitignored build output, so the field is dropped rather than repointed.

All three templates also carried the description 'an mcp-use server'.
--list-templates reads that field, so the three were indistinguishable
from the CLI, and every generated project inherited the same string.
Each now says what it actually gives you.

Closes #2080
Closes #2081

* chore: add changeset for the template package.json fixes

* fix(create-mcp-use-app): stop discarding the template description

updatePackageJson overwrote description with a generic
"<name>: an mcp-use server" on every scaffold, so the per-template
descriptions only ever reached --list-templates and never the generated
project. It now fills that in only when the template has no description
of its own, which keeps the previous behaviour for templates without one.

* chore(typescript): version packages (canary)

* fix(client): stop leaking parent env to stdio servers (#2125)

Port the security fix from #1949 to the v2 client package and verify the child process receives only safe defaults plus explicitly configured variables.

Co-authored-by: VihaanAgarwal <72850668+VihaanAgarwal@users.noreply.github.com>

* chore(typescript): version packages (canary)

* fix(client): bound conformance auth scenarios (#2126)

* fix(client): make stdio errlog actually receive the child's stderr (#2086)

* fix(client): make stdio errlog actually receive the child's stderr

StdioConnectionManager takes an errlog stream and documents that the
child server's stderr is piped to it, but the transport was created
without stderr: "pipe". The SDK defaults to "inherit", which leaves
transport.stderr null, so the forwarding block guarding on it never
ran and the child's stderr always went to the parent instead.

Spawn with stderr: "pipe" by default, spread so an explicit mode in
server params still wins. Tests spawn real child processes: one checks
a custom errlog receives the output, one checks stderr: "ignore" still
opts out.

* chore: drop stray version.ts that does not belong on beta

Left over from a main checkout; packages/mcp-use does not exist on this
branch.

* fix(client): expose stderr mode on the public stdio APIs

Per review, the compatibility escape hatch only worked for callers that
built StdioConnectionManager directly. StdioConnector did not accept or
forward stderr and StdioServerConfig did not expose it, so users of the
normal public APIs could not opt back into inherited stderr.

- Add a StdioStderrMode of "pipe" | "inherit" | "ignore", default "pipe".
- Accept it on StdioConnector and StdioServerConfig, forward it into
  StdioServerParameters, and thread it through the config path.
- Apply the default after the spread so an explicit stderr: undefined no
  longer defeats it.
- Only forward transport.stderr when the mode leaves a readable stream.
- Pipe with { end: false } and unpipe on close, since errlog is
  caller-owned and may be reused across reconnects.
- Handle stream errors instead of letting a destroyed errlog surface as
  an unhandled 'error' event.

Tests now start the transport before asserting, so the non-pipe cases are
exercised against a real child instead of passing by construction.

* fix(client): handle errlog write errors

---------

Co-authored-by: Andrew Khadder <andrew@manufact.com>

* chore(typescript): version packages (canary)

* fix(inspector): block loopback proxy targets by default (#2134)

mountInspector defaulted oauthProxyAllowLoopback to true, and the standalone
CLI hardcoded it — including in the published Docker image, which runs the
CLI with NODE_ENV=production on a public port. A publicly reachable inspector
could therefore proxy requests to the host's loopback services (SSRF), while
RFC1918/metadata targets were already blocked.

- mountInspector: default allowLoopback to false; local dev tooling opts in
- CLI: allow loopback unless NODE_ENV=production; INSPECTOR_ALLOW_LOOPBACK
  overrides either way
- Express-adapter test opts in explicitly (it proxies to its own 127.0.0.1
  echo server); new regression test covers the default and the opt-in

* chore(typescript): version packages (canary)

* docs: add v2 changelog updates

* chore: remove retired beta release flow (#2141)

* fix: keep prerelease versioning visible to Knip (#2142)

* fix: patch dependency vulnerabilities (#2151)

* fix: patch vulnerable dependencies

* fix: use mcp-use in client demo servers

* chore(typescript): version packages (canary)

---------

Signed-off-by: Andrew Khadder <54488379+khandrew1@users.noreply.github.com>
Co-authored-by: Ayaan Gazali <ayaangazali.work@gmail.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Enrico Toniato <2827496+tonxxd@users.noreply.github.com>
Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>
Co-authored-by: VihaanAgarwal <72850668+VihaanAgarwal@users.noreply.github.com>
 2026-08-05 10:26:37 -07:00
Andrew Khadder 8d856b6034 docs(typescript): add TypeDoc generation and source API docs (#2039) 
* docs(typescript): document public source APIs

* chore(typescript): enforce TSDoc syntax

* docs(typescript): add TypeDoc generation
 2026-07-28 11:53:40 -07:00
Pietro Zullo e6ba394ec7 chore: format adapter files for ruff 0.15 + remove docs PR comment spam (#1003) 
- Format 3 adapter files to match ruff 0.15 (CI version)
- Remove the PR comment step from docs.yml that spammed every push
 2026-02-14 18:53:20 -08:00
Enrico Toniato 4810f02733 fix(ci): use commit SHA instead of branch name for fork PR checkouts 
- Changed from github.event.pull_request.head.ref to head.sha
- Fixes 'branch could not be found' error for contributor fork PRs
- Works for fork PRs, same-repo PRs, and direct pushes
 2026-01-11 08:38:49 +01:00
Harshith VH 28e104a6a4 fix checkout step (#408) 2025-11-03 18:30:40 +01:00
Vincenzo Reina 7d3a3040a9 feat: Adapter integrations (#325) 
* feat: openai, anthropic, google adapters

* feat: adapters examples and documentation

* feat: update imports

* fix: release drafter action

* docs: header change

* chore: locked langchain dependencies in pyproject.toml (#321)

* python/release/1.3.13

* feat: Update langchain adapter

* feat: Update MCPAgent

* feat: General fixes

* feat: Correct naming

* feat: Fix formatting

* feat: Add genai dependency

* feat: Fix documentation

* feat: Fix imports

* logo

* icons

* Update docs/python/integration/google.mdx

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Signed-off-by: Pietro Zullo <62951181+pietrozullo@users.noreply.github.com>

* feat: Critical bug fixes

* chore: local logos

* chore: moved icons

* fix: Lambda closure issue

* docs: Add steps

* docs: Fix documentation

* fix docs action

* fix attempt 2

* docs: update

* chore: google optional dependency

* chore: minor docs changes

* fix generate docs script

* fix: lint

* import guard in __init__ file

* ci: install google-genai in docs workflow

* chore: print diffs

* chore: fix action checkout ref

---------

Signed-off-by: Vincenzo Reina <vincenzoreinaa05@gmail.com>
Signed-off-by: Pietro Zullo <62951181+pietrozullo@users.noreply.github.com>
Co-authored-by: pietrozullo <pietro.zullo@gmail.com>
Co-authored-by: Pietro Zullo <62951181+pietrozullo@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
 2025-10-22 07:37:29 +02:00
Luigi Pederzani 5a1eacf82b move workflows 2025-10-15 19:21:00 +02:00