Vexly MCP Server

Vexly exposes a public MCP endpoint so desktop tools and agent workflows can call the Vexly agent through a standard MCP tool surface.

Endpoint

Remote MCP endpoint:

https://api.vexly.io/api/v1/public/mcp

Current v1 tool surface:

• vexly.run

Default wait behavior:

• Vexly MCP waits up to 180 seconds by default before returning a still-running run handle.
• You can override that by passing timeout_seconds in the vexly.run tool call.

When to Use Remote MCP

Use remote MCP when your client can handle:

• HTTP MCP transport
• bearer auth
• browser or OAuth-based login

If Your Client Does Not Handle Remote MCP Well

Use the public API or the reference CLI helper instead.

Public Repo

Reference configs and docs live here:

• mcp/README.md
• docs/mcp.md

Auth

Use one of these:

• PAT for quick setup
• device flow for CLI-based flows
• OAuth bearer tokens for clients with stronger remote auth support

See Authentication.