Versions: * arcade-mcp\==1.0.0rc1 * arcade-mcp-server\==1.0.0rc1 * arcade-core\==2.5.0rc1 * arcade-tdk\==2.6.0rc1 * arcade-serve\==2.2.0rc1 ### Summary Adds first-class MCP support across Arcade, introduces a new MCP server and CLI, unifies the project under the arcade-mcp name, overhauls templates/scaffolding, and improves developer tooling, secrets management, and examples. ### Highlights - **MCP Server & Core** - New MCP server with stdio and HTTP/SSE transports, session management, resumability, and lifecycle handling. - FastAPI-like `MCPApp` for building servers with lazy init; integrated worker+MCP HTTP app option. - Middleware system (logging and error handling), robust exception hierarchy, and Pydantic-based settings. - Async-safe managers for tools, resources, and prompts backed by registries and locks. - Developer-facing, transport-agnostic runtime context interfaces (logs, tools, prompts, resources, sampling, UI, notifications). - Conversion from Arcade ToolDefinition to MCP tool schema; OpenAI JSON tool schema converter. - Parser supports `@app.tool`/`@app.tool(...)` decorators. - **CLI** - New `mcp` command to run MCP servers with stdio or HTTP/SSE. - New `secret` command to set/list/unset tool secrets (supports .env input, preserves original casing for lookups). - `new` command refactored; option to create a full toolkit package with scaffolding. - `chat` command removed. - `serve.py` imports updated to `arcade_serve.fastapi.telemetry`; version retrieval now uses `arcade-mcp`. - `show.py` refactor to use new local catalog utilities. - `display_tool_details` improved: adds “Default” column and handles nested properties. - **Configuration & Discovery** - New `configure.py` to set up Claude Desktop, Cursor, and VS Code to connect to local or Arcade Cloud MCP servers. - Discovery utilities to find/install toolkits, build `ToolCatalog`s, analyze files for tools, load kits from directories (pyproject parsing), and build minimal toolkits. - Better handling of provider API key resolution and evaluation suite loading. - **Templates & Scaffolding** - Reorganized template structure (minimal vs full); moved `.pre-commit-config.yaml`, `.ruff.toml`, license, Makefile, README, tests, and tools layout to correct paths. - Minimal template adds `.env.example` for runtime secret injection. - Template pyproject updated for MCP servers; includes sample server with greeting and secret-reveal tools. - Authorization flow in templates simplified. - **Repo-wide Renaming & Examples** - Migrates references from `arcade-ai` to `arcade-mcp` across READMEs, scripts, and package metadata. - Examples updated (LangChain/LangGraph/AI SDK/TypeScript) and package name changed to `arcade-mcp-sdk`. - **Evals & Core Utilities** - Evals now use OpenAI tooling format (`OpenAIToolList`, `to_openai`); `tool_eval` takes `provider_api_key`. - Core utilities: fixed `does_function_return_value` by dedenting before parse; version bump to `2.5.0rc1` and dependency cleanup. - **Tooling & CI** - `setup-uv-env` action splits toolkit vs contrib dependency installation. - Pre-commit: excludes `libs/arcade-mcp-server/mkdocs.yml` and `libs/tests/` from YAML and Ruff hooks; Ruff per-file ignores (e.g., C901 in `libs/**/*.py`, TRY400 in server docs paths). - Makefile updates for uv env setup, quality checks, tests, builds, and new `shell` target. - Added Makefile to MCP server library to streamline dev workflow. - **Cleanup** - Removed `claude.json` config. - Simplified stdio entrypoint; removed unused imports (`arcade_gmail`, `arcade_search`). ### Breaking Changes - **CLI**: `chat` command removed; use `mcp`, `secret`, and updated `new`. - **Naming**: All users should update references from `arcade-ai` to `arcade-mcp`. - **Templates**: File paths moved; downstream scripts referencing old template locations may need updates. ### Getting Started - Run an MCP server: - `arcade mcp --stdio --toolkits your_toolkit` - `arcade mcp --http --toolkits your_toolkit` - Manage secrets: - `arcade secret set your_toolkit KEY=value` - `arcade secret list your_toolkit` - `arcade secret unset your_toolkit KEY` - Configure clients: - `arcade configure` to set up Claude Desktop, Cursor, and VS Code for local/Arcade Cloud MCP. --------- Co-authored-by: Sam Partee <sam@arcade-ai.com> Co-authored-by: Shub <125150494+shubcodes@users.noreply.github.com>
161 lines
4.2 KiB
Python
161 lines
4.2 KiB
Python
TOOLKIT_PAGE = """{header}
|
|
|
|
{table_of_contents}
|
|
|
|
{tools_specs}
|
|
{reference_mdx}
|
|
{footer}
|
|
"""
|
|
|
|
TOOLKIT_HEADER = """# {toolkit_title}
|
|
|
|
import ToolInfo from "@/components/ToolInfo";
|
|
import Badges from "@/components/Badges";
|
|
import TabbedCodeBlock from "@/components/TabbedCodeBlock";
|
|
import TableOfContents from "@/components/TableOfContents";
|
|
import ToolFooter from "@/components/ToolFooter";
|
|
|
|
<ToolInfo
|
|
description="Enable agents to interact with {toolkit_title}"
|
|
author="Arcade"
|
|
{auth_type}
|
|
versions={{["{version}"]}}
|
|
/>
|
|
|
|
<Badges repo="arcadeai/{pip_package_name}" />
|
|
|
|
{description}"""
|
|
|
|
TABLE_OF_CONTENTS = """## Available Tools
|
|
|
|
<TableOfContents
|
|
headers={{["Tool Name", "Description"]}}
|
|
data={{
|
|
[{tool_items}
|
|
]
|
|
}}
|
|
/>
|
|
|
|
<Tip>
|
|
If you need to perform an action that's not listed here, you can [get in touch
|
|
with us](mailto:contact@arcade.dev) to request a new tool, or [create your
|
|
own tools](/home/build-tools/create-a-toolkit).
|
|
</Tip>"""
|
|
|
|
TABLE_OF_CONTENTS_ITEM = '\n ["{tool_fully_qualified_name}", "{description}"],'
|
|
|
|
TOOL_SPEC = """## {tool_fully_qualified_name}
|
|
|
|
<br />
|
|
{tabbed_examples_list}
|
|
|
|
{description}
|
|
|
|
**Parameters**
|
|
|
|
{parameters}
|
|
{secrets}
|
|
"""
|
|
|
|
TOOL_SPEC_SECRETS = """**Secrets**
|
|
|
|
This tool requires the following secrets: {secrets} (learn how to [configure secrets](/home/build-tools/create-a-tool-with-secrets#supplying-the-secret))
|
|
"""
|
|
|
|
TABBED_EXAMPLES_LIST = """<TabbedCodeBlock
|
|
tabs={{[
|
|
{{
|
|
label: "Call the Tool Directly",
|
|
content: {{
|
|
Python: ["/examples/integrations/toolkits/{toolkit_name}/{tool_name}_example_call_tool.py"],
|
|
JavaScript: ["/examples/integrations/toolkits/{toolkit_name}/{tool_name}_example_call_tool.js"],
|
|
}},
|
|
}},
|
|
]}}
|
|
/>"""
|
|
|
|
TOOL_PARAMETER = "- **{param_name}** ({definition}) {description}"
|
|
|
|
TOOLKIT_FOOTER = """<ToolFooter pipPackageName="{pip_package_name}" />"""
|
|
|
|
TOOLKIT_FOOTER_OAUTH2 = """## Auth
|
|
|
|
{provider_configuration}
|
|
|
|
<ToolFooter pipPackageName="{pip_package_name}" />
|
|
"""
|
|
|
|
WELL_KNOWN_PROVIDER_CONFIG = "The Arcade {toolkit_name} toolkit uses the [{provider_name} auth provider](/home/auth-providers/{provider_id}) to connect to users' {toolkit_name} accounts. Please refer to the [{provider_name} auth provider](/home/auth-providers/{provider_id}) documentation to learn how to configure auth."
|
|
|
|
GENERIC_PROVIDER_CONFIG = "The {toolkit_name} toolkit uses the Auth Provider with id `{provider_id}` to connect to users' {toolkit_name} accounts. In order to use the toolkit, you will need to configure the `{provider_id}` auth provider."
|
|
|
|
TOOL_CALL_EXAMPLE_JS = """import {{ Arcade }} from "@arcadeai/arcadejs";
|
|
|
|
const client = new Arcade(); // Automatically finds the `ARCADE_API_KEY` env variable
|
|
|
|
const USER_ID = "{{arcade_user_id}}";
|
|
const TOOL_NAME = "{tool_fully_qualified_name}";
|
|
|
|
// Start the authorization process
|
|
const authResponse = await client.tools.authorize({{tool_name: TOOL_NAME}});
|
|
|
|
if (authResponse.status !== "completed") {{
|
|
console.log(`Click this link to authorize: ${{authResponse.url}}`);
|
|
}}
|
|
|
|
// Wait for the authorization to complete
|
|
await client.auth.waitForCompletion(authResponse);
|
|
|
|
const toolInput = {input_map};
|
|
|
|
const response = await client.tools.execute({{
|
|
tool_name: TOOL_NAME,
|
|
input: toolInput,
|
|
user_id: USER_ID,
|
|
}});
|
|
|
|
console.log(JSON.stringify(response.output.value, null, 2));
|
|
"""
|
|
|
|
TOOL_CALL_EXAMPLE_PY = """import json
|
|
from arcadepy import Arcade
|
|
|
|
client = Arcade() # Automatically finds the `ARCADE_API_KEY` env variable
|
|
|
|
USER_ID = "{{arcade_user_id}}"
|
|
TOOL_NAME = "{tool_fully_qualified_name}"
|
|
|
|
auth_response = client.tools.authorize(
|
|
tool_name=TOOL_NAME,
|
|
user_id=USER_ID,
|
|
)
|
|
|
|
if auth_response.status != "completed":
|
|
print(f"Click this link to authorize: {{auth_response.url}}")
|
|
|
|
# Wait for the authorization to complete
|
|
client.auth.wait_for_completion(auth_response)
|
|
|
|
tool_input = {input_map}
|
|
|
|
response = client.tools.execute(
|
|
tool_name=TOOL_NAME,
|
|
input=tool_input,
|
|
user_id=USER_ID,
|
|
)
|
|
print(json.dumps(response.output.value, indent=2))
|
|
"""
|
|
|
|
ENUM_MDX = """## Reference
|
|
|
|
Below is a reference of enumerations used by some of the tools in the {toolkit_name} toolkit:
|
|
|
|
{enum_items}
|
|
"""
|
|
|
|
ENUM_ITEM = """## {enum_name}
|
|
|
|
{enum_values}
|
|
"""
|
|
|
|
ENUM_VALUE = "- **{enum_option_name}**: `{enum_option_value}`"
|