Troubleshooting

API key is missing

Meaning:

• the MCP URL did not include api_key
• the API token was not added to the URL

Fix:

• create or copy an API token in Settings > API tokens
• add ?api_key=<api-token> to the MCP URL

Team id is required

Meaning:

• the API tool call needs team scope
• the MCP URL does not include a default team_id
• the tool call did not pass teamId

Fix:

• pass teamId to vrt_api_read or vrt_api_mutation
• or add team_id=<team-id> to the MCP URL as a default team

Mutation requests require confirm=true

Meaning:

• vrt_api_mutation was called without explicit confirmation

Fix:

• add confirm: true only when you intend to write data in the connected environment

API Discovery Search Is Rejected

Meaning:

• vrt_product_help_search received an endpoint, field, schema, or payload discovery question

Fix:

• read vrt://api/openapi-context
• then read vrt://api/path/<encoded-path>
• then read vrt://api/path/<encoded-path>/<method>

Client Shows No Tools

Check:

• the URL points at /
• the URL includes api_key
• the client uses Streamable HTTP transport
• the client is allowed to connect to remote MCP servers

Wrong Or Empty API Data

Check:

• the credentials exist in the environment used by the MCP host
• the team id exists in the environment used by the MCP host
• the request has the expected default team_id or tool-level teamId
• the endpoint shape came from vrt://api/openapi-context, not guessed memory