> ## Documentation Index
> Fetch the complete documentation index at: https://social-b97141fb-auto-generate-llmstxt.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Run Vise as an MCP server
> Expose Vise's local tools to Claude Code, Cursor, Codex, and VS Code over MCP.
Vise ships an MCP adapter, so any MCP-capable host can call Vise's tools — inspect, plan, assess Day-2 impact, check SDK and organization-policy boundaries, verify runtime receipts, compose Passports, validate, run sensors, and look up docs — directly during the coding loop. Start it with:
```sh theme={null}
vise mcp
```
This runs a local **stdio** MCP server. You normally don't run it by hand; you register the command in your host's MCP configuration and the host launches it for you.
This is different from the hosted **docs** MCP server at `https://learn.social.plus/mcp` ([overview](/ai/docs-mcp-server)). That one is remote (SSE) and only reads documentation. The Vise MCP server runs **locally** and exposes Vise's validation and planning tools against the repository you're working in. You can use both at once.
## Prerequisites
Install Vise so the `vise` command is on your `PATH`:
```sh theme={null}
npm install -g @amityco/social-plus-vise
vise doctor
```
If you prefer not to install globally, replace the command below with `npx` and args `["-y", "-p", "@amityco/social-plus-vise", "vise", "mcp"]`.
## Configure your host
Add a project-scoped `.mcp.json` in your repository root:
```json theme={null}
{
"mcpServers": {
"social-plus-vise": {
"command": "vise",
"args": ["mcp"]
}
}
}
```
Add `.cursor/mcp.json` in your project root:
```json theme={null}
{
"mcpServers": {
"social-plus-vise": {
"command": "vise",
"args": ["mcp"]
}
}
}
```
Add `.vscode/mcp.json` in your project (VS Code uses a `servers` key):
```json theme={null}
{
"servers": {
"social-plus-vise": {
"command": "vise",
"args": ["mcp"]
}
}
}
```
Add the server to `~/.codex/config.toml`:
```toml theme={null}
[mcp_servers.social-plus-vise]
command = "vise"
args = ["mcp"]
```
Restart or reload the host after editing its configuration, then confirm `social-plus-vise` appears as an available MCP server.
## What it exposes
The Vise MCP tools mirror the [CLI commands](/ai/vise/cli-reference), named in snake\_case. The ones you'll use most:
| Tool | Mirrors | Purpose |
| - | - | - |
| `inspect_project` | `vise inspect` | Detect platform, surfaces, sensors, and complete-scan coverage |
| `impact_project` | `vise impact` | Explain Day-2 change impact, evidence freshness, reported cross-surface symptoms, and the smallest safe next actions without editing |
| `analyze_sdk_release` | `vise sdk-release` | Explain exact-snapshot SDK assurance or diff two extracted SDK surface snapshots |
| `plan_integration` | `vise plan` | Grounded plan with docs citations and intake |
| `init_compliance` | `vise init` | Write the `sp-vise/` contract |
| `check_compliance` | `vise check` + lifecycle summary | Validate the code against the contract and add the same `customerOperations` build, Day-2, and release routing returned by CLI `vise status` |
| `assess_policy_operations` | `vise policy status` | Read the repository policy source, lifecycle and trust state, deterministic update impact, and exact owner routing |
| `verify_runtime_receipt` | `vise smoke verify` | Verify retained source/build/runner/surface/artifact/Passport bindings without relaunching the app |
| `generate_integration_passport` | `vise passport` | Compose a digest-bound, sanitized integration handoff; read-only unless writing is explicit |
| `verify_integration_passport` | `vise passport verify` | Recompute Passport claims and local evidence hashes without repairing the project |
| `compare_integration_passports` | `vise passport compare` | Compare handoffs and compose the Governed Release Review decision |
| `verify_trust_envelope` | `vise trust verify` | Authenticate a Passport or Policy Pack envelope against an explicit local trust policy |
| `run_sensors` | `vise run-sensors` | Run detected build, lint, typecheck, and smoke checks; explicitly included sensor names must match |
| `get_sdk_facts` | `vise sdk-facts` | Read grounded SDK surface facts |
| `search_docs` / `get_doc_page` | `vise search-docs` / `vise get-doc-page` | Find and read social.plus docs |
| `debug_issue` | `vise debug` | Diagnose an SDK-specific runtime failure |
| `attest_rule` / `explain_rule` | `vise attest` / `vise explain` | Record evidence and read rule guidance |
| `record_learning` / `show_learning` | `vise learning record` / `vise learning show` | Record and read local-only, advisory learning and Outcome Evidence |
`check_compliance` keeps its established compliance fields and exit code; `customerOperations` is additive and read-only. It does not run sensors, write files, gate on advisory findings, or infer human approval.
Signing trust envelopes, accepting an organization policy source, and installing Managed Placements are intentionally CLI-only. An MCP host can verify an envelope or assess policy, but Vise does not expose private-key signing or controlled policy acceptance through MCP.
## Skill or MCP?
The [skill](/ai/vise/overview#get-started) and the MCP server are complementary:
* The **skill** teaches the agent *when* to inspect, plan, fetch docs, validate, and attest.
* The **MCP server** exposes the *tools* the agent calls to do it.
For MCP-capable hosts, install the skill **and** register the MCP server. On hosts without MCP support, install the skill and let the agent call the `vise` CLI directly.
## Related
Install Vise and run your first integration.
The governed loop and how to read a check result.
The full command set behind these tools.
Connect an AI tool to the hosted documentation MCP server.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.