# Auth.md

OutreachGenie authentication for agents.

Public product pages, guides, tools, and discovery documents can be read without signing in. Private workspace records and MCP tools require the user's authorization.

## Discover the live service

- MCP endpoint: https://api.outreachgenie.ai/mcp
- OAuth authorization server metadata: https://api.outreachgenie.ai/.well-known/oauth-authorization-server
- MCP protected resource metadata: https://api.outreachgenie.ai/.well-known/oauth-protected-resource/mcp
- MCP server card: https://www.outreachgenie.ai/.well-known/mcp/server-card.json
- OpenAPI specification: https://www.outreachgenie.ai/openapi.json
- Setup and API documentation: https://www.outreachgenie.ai/developers

Fetch the live metadata to discover authorization, token, registration, and revocation endpoints and supported scopes. The authorization server is on api.outreachgenie.ai; the public website is not a separate OAuth issuer.

## Connect with user approval

Use an MCP client that supports OAuth authorization code flow with PKCE S256. Open the discovered authorization URL in the user's browser. The user signs in and approves access to the intended workspace. Request only the scopes needed for the task; request offline access only when the user needs a persistent connection. Never request a user's password or LinkedIn session cookies in chat.

For an existing workspace API key, use the documented bearer authentication flow. Keep keys and OAuth tokens in the client's secret storage and send them only in the Authorization header to the documented API or MCP service. Never put credentials in URLs, public files, or logs.

## Handle authorization failures

A 401 response requires authentication or session renewal. Read the WWW-Authenticate resource_metadata link to discover the protected resource's requirements. A 403 response indicates insufficient scope or workspace permission; do not repeatedly retry or attempt to bypass it. Ask the user to review the requested access. Stop using a connection when the user revokes it.

## Respect workspace permissions

Authentication does not authorize every operation. Start with read-only inspection. Obtain the user's approval for imports, record changes, campaign activation, outreach messages, and publishing. Show the intended people, content, and action before running it. Follow the scope and workspace permissions returned by the service.