MCP Connector
Bring your venture's business context into Claude and other AI tools you already use.
The Vora IQ connector is built on the Model Context Protocol (MCP), an open standard for giving AI applications access to outside context. Connect it once, and the AI client grounds its work in your actual business — copy in your brand voice, designs in your exact colors with your real logo, messaging aimed at the customers you actually serve. No more pasting brand guidelines into every chat.
The connector is read-only: a connected client can read your context but can never create, modify, or delete anything in your Vora IQ account.
What the connector shares
A connected AI client can read exactly five resources from your venture's Business Context Layer — nothing else:
| Resource | What the AI client gets |
|---|---|
| Brand voice | Your tone description and writing constraints, applied to all copy it generates |
| Brand kit | Your color palette, logo, and recent brand assets — real values instead of placeholders |
| Customer segments | Who you serve: target segments with pain points and jobs-to-be-done |
| Positioning | Business summary, value propositions, target segment, and pricing model |
| Hook framework | Vora's seven-layer social post structure and ranked hook formulas from the Echo agent |
Each connection is scoped to a single venture — the one you approve when you connect. Payment information, connected account data, conversations, and everything else in your account stay out of reach.
Before you connect
- •A Vora IQ account with at least one venture
- •Business context filled in for that venture — a resource you haven't completed in Vora IQ (for example, brand voice) comes back empty to the AI client
- •An MCP-capable client — Claude (web and desktop, on paid plans), Lovable, or any client that supports remote MCP servers
Connect from Claude
- In Claude, open Settings → Connectors and choose Add custom connector
- Enter the connector URL:
https://mcp.voraiq.ai/mcp - Click Connect — you'll be sent to Vora IQ to sign in with your usual account
- Choose the venture you want to share and approve the connection
That's the whole setup. Other MCP clients work the same way: point them at the URL above and they discover the sign-in flow automatically.
Try it
- •"Write the hero section for our new landing page in our brand voice."
- •"Draft five launch posts using our hook framework."
- •"Mock up a pricing page with our brand colors and logo."
- •"Which of our customer segments cares most about this feature? Write the announcement for them."
Managing access
Switching ventures. A connection is bound to the venture you approved. To work with a different venture, remove the connector in your AI client and connect again, choosing the other venture at the consent step.
Revoking access. Remove the connector in the AI client at any time to end its access. Access tokens expire automatically within 24 hours and refresh tokens within 30 days. To have a grant revoked immediately, email privacy@voraiq.com.
Troubleshooting
- •The connection fails or asks you to authorize repeatedly. Remove the connector, add it again with the exact URL
https://mcp.voraiq.ai/mcp, and complete the full sign-in including the venture approval step. - •The client reports an authorization error after a quiet month. Connections expire after 30 days without use. Reconnect to start a fresh grant.
- •A resource comes back empty. That section of your business context hasn't been completed in Vora IQ yet. Fill it in (for example, brand voice or positioning) and ask again.
- •Recent edits aren't showing up. Context is cached briefly for speed. Changes appear within an hour at most — usually within minutes.
- •"Rate limit exceeded." The connector limits how many reads a client can make per minute. Wait a moment and retry.
Security and data handling
- •Authorization uses OAuth 2.1 with PKCE and dynamic client registration; all traffic is encrypted with TLS
- •The connector service never stores your business context — it reads from Vora IQ on demand and holds only hashed OAuth tokens
- •Every read is recorded in an audit log (which resource, when, by which client) retained for 12 months
- •Once context is delivered to an AI client at your direction, it is handled under that client's own privacy policy
Full details are in Section 5.1 of our Privacy Policy.
Technical reference
| Endpoint | https://mcp.voraiq.ai/mcp |
| Transport | Streamable HTTP |
| Authentication | OAuth 2.1 (PKCE, dynamic client registration) |
| Capabilities | Read-only resources — no tools, no write access |
Stuck on something this page doesn't cover? Email hello@voraiq.com and we'll get you connected.