Nekt Express
Nekt Express
Step 1: Enable the MCP Server
Go to Integrations → MCP Server and click Configure. Then, Enable MCP Server. Nekt will provision the server automatically.Step 2: Create tokens
Once the server is active, go to the MCP Tokens section and create one or more access tokens. Each token can be scoped to a specific set of tables, or granted full access based on the creating user’s permissions.If you connect via OAuth and don’t have any tokens yet, one will be automatically created with the same permissions as your user account.GCP
GCP
Step 1: Enable the MCP Server
Go to Settings → Cloud and click Enable MCP Server. The server is provisioned as a Google Cloud Run Service in your GCP project.Step 2: Create tokens
Once the server is active, go to the MCP Tokens section and create one or more access tokens. Each token can be scoped to a specific set of tables, or granted full access based on the creating user’s permissions.If you connect via OAuth and don’t have any tokens yet, one will be automatically created with the same permissions as your user account.AWS
AWS
Step 1: Enable the MCP Server
Go to Settings → Cloud and click Enable MCP Server. Enter the full domain you want to use as your MCP server endpoint — for example,mcp.company.co, not just company.co.Step 2: Verify the HTTPS certificate
Add the CNAME record provided by Nekt to your DNS provider to validate the HTTPS certificate. Allow 5–10 minutes for verification.Step 3: Add the MCP URL to your DNS
Still in your DNS provider, add the second CNAME record to point your custom domain to the MCP server. Allow an additional 5–10 minutes for this to propagate.Your MCP server is now live.Step 4: Create tokens
Go to the MCP Tokens section and create one or more access tokens. Each token can be scoped to a specific set of tables, or granted full access based on the creating user’s permissions.If you connect via OAuth and don’t have any tokens yet, one will be automatically created with the same permissions as your user account.Infrastructure
Nekt Express
Nekt Express
Managed by Nekt and billed through your Nekt credits.
GCP
GCP
The MCP Server runs on Google Cloud Run in your GCP project. Costs are based on Cloud Run’s per-second billing model for CPU and memory while instances are active. With typical usage, expect approximately $20–25/month. The server scales to zero when idle, so actual costs depend on how often it handles requests.Services used:
- Cloud Run — 1 vCPU, 2 GiB memory, scales to zero when idle
- Secret Manager — stores server credentials
AWS
AWS
The MCP Server runs on AWS Fargate in your AWS account as an always-on service. In
us-east-1, the fixed cost is approximately $34/month.Services used:- AWS Fargate — 0.5 vCPU, 2 GiB memory
- Network Load Balancer — routes HTTPS traffic to the server
- AWS Secrets Manager — stores server credentials
Prerequisites
If your workspace runs on your own cloud account, your infrastructure must be updated to the minimum version below before enabling the MCP Server.| Cloud | Minimum version |
|---|---|
| Nekt Express | No requirement — always up to date |
| AWS | CloudFormation 2.0.26 |
| GCP | Terraform 1.0.4 |
You can check your current cloud version in Settings → Cloud.