Cursor is an AI-powered code editor. When connected to Nekt through the MCP Server, it can query and analyze your data directly while you code. The connection uses bearer token authentication via Cursor’s mcp.json configuration.
Requires a paid Nekt plan (for MCP Server access) and Cursor installed.
1. Activate your MCP Server
The connection is made by activating the MCP Server in your workspace. Check this guide for instructions.
2. Get your endpoint and token
Go to Integrations > MCP Server in the Nekt platform. You’ll need two values:
- Endpoint — the MCP server URL displayed at the top of the page
- Token — a bearer token created in the MCP Tokens section
If you don’t have a token yet, create one. You can scope it to specific tables or grant full access.
Tokens created manually can be scoped to specific tables for fine-grained access control. Tokens grant Cursor access only to the tables associated with that token.
3. Connect Cursor to Nekt
Open Cursor's MCP settings
In Cursor, open Settings → Tools & Integrations → MCP, then click Add new MCP server. This opens (or creates) the configuration file.You can also edit the file manually:
- Global (available in every project):
~/.cursor/mcp.json
- Project-scoped (committed with the repo):
.cursor/mcp.json in the project root
Add the Nekt MCP server
Add the following block to mcp.json:Replace MCP_ENDPOINT with the endpoint from the MCP Server page and MCP_TOKEN with the token you created.To avoid storing the token in plaintext, set it as an environment variable in your shell profile and reference it with ${env:NEKT_MCP_BEARER_TOKEN} in the headers value. This is especially important for project-scoped mcp.json files committed to version control.
Verify the connection
Go back to Settings → Tools & Integrations → MCP. The nekt server should appear with a green status indicator and the list of available tools.You should see the nine tools provided by the Nekt MCP Server. You can learn more about them here.
4. Explore your data
Once connected, ask Cursor’s chat a question about your data. For example:
Cursor will use the MCP tools to query your data and return an answer.
We’d love to know what you’re building with Nekt! Share your projects with us through any of our communication channels.
Privacy & Security
Your data privacy is a core principle of the Nekt platform.
When you connect Cursor to Nekt through the MCP Server, Cursor does not receive direct database credentials or unrestricted access to your infrastructure. Instead, Cursor interacts with your data exclusively through the secure tools exposed by the Nekt MCP Server, which act as a controlled gateway to the Nekt API. These tools enforce the same authentication, authorization, and permission rules used throughout the Nekt platform.
Access is scoped using tokens and user permissions, meaning Cursor can only access the tables and actions explicitly allowed by the token you configured. This architecture ensures that all queries, analysis, and data interactions remain governed, auditable, and restricted to your workspace permissions.
When using Cursor, your interactions are subject to Cursor’s privacy settings and policies. We recommend reviewing the official Cursor privacy documentation to understand their data handling policies and selecting the configuration that best aligns with your organization’s security requirements.
Need help?
Contact our support team if you encounter issues during setup. 
