# Use these docs with Context7

> Find Menace Voice documentation in Context7 without confusing documentation access with workspace control.

## Documentation lookup

Context7 retrieves documentation for AI coding assistants. Resolve **Menace Voice** with the Context7 library-resolution tool, choose the result for `drewsephski/menace-voice`, and query a specific topic. For example: “How do I publish a draft before placing an outbound call?”

Use the library ID returned by Context7. Availability depends on successful indexing; if the library is not yet listed, use this site's Markdown endpoints directly.

## Direct machine-readable docs

Docs7 generates these endpoints relative to this site's root:

| Endpoint | Use |
| --- | --- |
| `/llms.txt` | Page discovery with Markdown links |
| `/llms-full.txt` | The complete documentation corpus |
| `/<page>.md` | One page as Markdown |
| `/search?q=webhooks` | Documentation search as JSON |
| `/.well-known/agent-skills/index.json` | Agent skill discovery |

Resolve URLs against the official docs host, not the Menace Voice application API host. Regular page URLs also support `Accept: text/markdown`.

## Three separate connections

- **Context7** reads documentation to support an implementation task.
- **Menace Voice workspace MCP** authenticates with your API key and can inspect or edit your workspace.
- **Remote MCP tools** are functions the voice agent can call during a conversation.

Finding a page in Context7 does not give the assistant access to your agents. Connecting workspace MCP does not automatically attach remote tools to a voice workflow.

Read [workspace MCP setup](/integrations/mcp) and [the MCP bridge](/handbook/agents/mcp-bridge) before authorizing workspace changes.