# Vindula MCP: conecte Claude e Codex à sua intranet | Vindula

> Conecte Claude, Codex e outros agentes MCP ao Vindula com OAuth, consentimento e permissões reais do usuário para trabalhar com a Biblioteca corporativa.

Source: https://vindula.ai/mcp

Vindula MCP

# Connect Claude, Codex, and other agents to Vindula

Use Vindula remote MCP to query and operate the corporate Library with OAuth, consent, and real user permissions.

 https://api.vindula.ai/mcp

 See how to connect Talk to an expert

## One URL, many agents

Paste the MCP URL into the client, sign in with your Vindula account, and approve access. No manual token and no shared password.

### Claude

Add a custom connector, paste the MCP URL, and sign in with your Vindula account.

### Codex CLI

Register the remote server and start OAuth login in the browser.

### Other MCP clients

Clients compatible with remote MCP over Streamable HTTP use the same URL.

Claude

- **1.** Open connectors/custom connector in Claude.
- **2.** Name it Vindula.
- **3.** Paste the MCP URL.
- **4.** Click connect, sign in, and approve access.

Codex CLI

```
codex mcp add vindula --url https://api.vindula.ai/mcp
codex mcp login vindula
```

Then ask Codex to search documents, list categories, or prepare safe Library actions.

What MCP enables

## Vindula Library inside the conversation

The agent works with high-level tools without bypassing governance, tenancy, or permissions.

### Search documents

The agent finds allowed content in the Vindula Library by term, category, and context.

### Operate safely

Declarative tools avoid free code execution and keep clear limits for every action.

### Respect permissions

OAuth scopes are consent. Real authorization remains in Vindula, by user and tenant.

## Scope is not final permission

Authorizing the connector does not grant superpowers. The server validates every call with the user's real Vindula permissions.

- No shared API key: the user signs in with OAuth and approves the connector.
- The client never sends company_id; company context comes from the server.
- Every operation goes through the user's real permissions and remains auditable.

## Frequently asked questions

 Does the agent become an admin?

No. Even if the client requests broad scopes, each action remains limited by the user's real Vindula permissions.

 Do I need to generate a manual token?

No. The flow uses OAuth: login, consent, and tokens managed by the MCP client.

 Does it work with Codex?

Yes. Use `codex mcp add vindula --url https://api.vindula.ai/mcp` and then `codex mcp login vindula`.