# MCP Explorer

The [MCP Explorer](https://developers.apideck.com/mcp-explorer) is a browser tool for the hosted Apideck MCP server at `https://mcp.apideck.dev/mcp`. It shows the exact JSON-RPC an agent sends in each server mode.

## Server modes

| Mode | Tools exposed | Initial context | Best for | Calls |
| --- | --- | --- | --- | --- |
| `dynamic` (default) | 4 meta-tools | ~1,300 tokens | General agents working across several APIs | `list_tools` → `describe_tool_input` → `execute_tool` |
| `code` | `apideck_search`, `apideck_run` | ~600 tokens | Agents that write code and chain several calls in one step | `apideck_search` → `apideck_run` (sandboxed JavaScript) |
| `static` | Every tool, registered directly | ~35–55K tokens | Focused agents on one API, combined with scope filters | `tools/list` → `tools/call` |

Choose a mode with `?mode=code` or `?mode=static` on the server URL; the Explorer accepts the same parameter (`https://developers.apideck.com/mcp-explorer?mode=code`). Static mode currently registers only the four workflow tools, on the hosted server and the CLI alike; full registration of the endpoint tools is pending, so use dynamic or code mode for endpoint calls.

## How the server is designed

- **Small context by default.** More than 380 tools across 12 domains would cost 35–55K tokens up front. Dynamic mode starts with four meta-tools and fetches one schema when needed, about 85% fewer tokens.
- **One tool per API operation.** Endpoint tools are named `<api>-<operation>`, for example `accounting-invoices-all`, and every API reference operation shows its tool name.
- **Workflows for multi-step jobs.** Tools such as the month-end close check, paying a bill or onboarding a hired applicant exist in every mode.
- **Safety enforced by the server.** `?scopes=read` (or `read,write`) hides everything else in every mode, including what `apideck_run` can call. `?lock_identity=true` pins the consumer and connection from the headers.

## What you can do

- Dynamic mode: browse tools by domain with `list_tools` (at most 50 per call, so search narrows with `search_terms`), read a tool's JSON Schema with `describe_tool_input` and run it with `execute_tool`.
- Code and static mode: load every tool with `tools/list` and call one directly with `tools/call`.
- Deep link to one tool: `https://developers.apideck.com/mcp-explorer?tool=accounting-invoices-all`. API reference operations link here from their MCP tool name.
- Copy an `mcp.json` for the mode and scope you picked.

## Credentials and safety

Browsing and schemas need no credentials. Running a tool sends your `x-apideck-api-key`, `x-apideck-app-id` and `x-apideck-consumer-id` (and optionally `x-apideck-service-id`) directly from the browser to the MCP server; values stay in the browser tab's session storage. The server authenticates with an API key; Vault session tokens (JWT) are not supported.

Runs are read-only by default: the Explorer adds `?scopes=read`, so the server refuses write and destructive tools. Writes need an explicit opt-in, and destructive tools a second confirmation.

## Related

- [MCP setup](https://developers.apideck.com/mcp.md)
- [MCP verification and recovery](https://developers.apideck.com/guides/mcp-verification-and-recovery.md)
- [API Explorer](https://developers.apideck.com/api-explorer.md)