Compatible with every major AI agent and IDE
What is the OpenFGA (Fine-Grained Auth) MCP Server?
Connect your OpenFGA instance to any AI agent to manage Relationship-Based Access Control (ReBAC) through natural conversation. OpenFGA is an open-source fine-grained authorization solution inspired by Google's Zanzibar.
What you can do
- Store Management — Create, list, and delete isolated stores to manage authorization data for different environments or applications.
- Authorization Modeling — Define and retrieve complex authorization models using types and relations to represent your system's permissions.
- Tuple Management — Write, read, and track changes to relationship tuples that define which users have which relations to specific objects.
- Relationship Checks — Instantly evaluate whether a user has a specific relation to an object (e.g., 'can user:anne view document:1?').
- Health Monitoring — Quickly check the status of your OpenFGA instance to ensure high availability.
How it works
- Subscribe to this server
- Enter your OpenFGA API URL and API Token (if applicable)
- Start managing your authorization logic from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Security Engineers — Audit relationship tuples and verify authorization models without manual API calls.
- Backend Developers — Quickly test and iterate on authorization models during development directly from the IDE.
- DevOps & SREs — Monitor store health and manage authorization environments across different clusters.
Built-in capabilities (16)
Perform multiple checks in one request
Check if a user has a relation to an object
Create a new OpenFGA store
Delete an OpenFGA store
Expand a relation into a tree
Get a specific authorization model
Get OpenFGA store details
Check OpenFGA server health
List authorization models
List all objects a user can access
List all OpenFGA stores
List all users who have a relation to an object
Read changes to relationship tuples
Query stored relationship tuples
Write a new authorization model
Add or delete relationship tuples
Why Cursor?
Cursor's Agent mode turns OpenFGA (Fine-Grained Auth) into an in-editor superpower. Ask Cursor to generate code using live data from OpenFGA (Fine-Grained Auth) and it fetches, processes, and writes. all in a single agentic loop. 16 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
OpenFGA (Fine-Grained Auth) in Cursor
OpenFGA (Fine-Grained Auth) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect OpenFGA (Fine-Grained Auth) to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for OpenFGA (Fine-Grained Auth) in Cursor
The OpenFGA (Fine-Grained Auth) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 16 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
OpenFGA (Fine-Grained Auth) for Cursor
Every tool call from Cursor to the OpenFGA (Fine-Grained Auth) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I check if a specific user has access to a resource?
You can use the check_relation tool. Provide the store ID and the relationship details (user, relation, and object) to get an immediate boolean response on whether the access is permitted.
Can I see the history of changes made to relationship tuples?
Yes, the read_changes tool allows you to retrieve the changelog of relationship tuples for a specific store, optionally filtered by object type.
How do I define a new authorization model?
Use the write_authorization_model tool. You will need to provide the store ID, the schema version, and a JSON array of type definitions that describe your relations.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Daftra
10 toolsEquip your AI agent to manage your ERP, accounting, and client relations directly via the Daftra API.

Capsulink
9 toolsManage shortened URLs via Capsulink — create links, track clicks, and monitor analytics directly from any AI agent.

Upstream Lens
8 toolsMonitor upstream oil and gas operations with production data analytics, well performance tracking, and field reporting tools.

Ask Kodiak
7 toolsSearch and manage commercial insurance products with Ask Kodiak — track carrier appetite and classifications via AI.
