mcp installation and env vars
the mcp server lets an assistant call hold your voice through local tool calls. it needs a live api key and a base url before the assistant can analyze, rewrite, or sync documents.
quick answer
set `HYV_API_KEY` and keep the key in the local mcp configuration, not inside prompts.
use this for
- installing the mcp server
- connecting codex, claude, or another mcp client
- debugging missing environment variables
steps
- create a scoped api key in hold your voice.
- add the key to the mcp client's secret environment as `HYV_API_KEY`.
- set `HYV_BASE_URL` only when using a non-production host.
- start the mcp server through the client.
- call the usage or profile tool first to confirm the key works.
details to know
- the default base url is the production hold your voice domain.
- mcp requests call the same rest api behind the scenes.
- tool errors usually map to api authentication, scope, plan, or validation errors.
limits and edge cases
- do not put the api key in a shared mcp config file unless that file is secret.
- a local mcp server cannot fix a key that is revoked or missing scopes.
ready to use the product instead of reading about it?
open app