Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.navisops.com/llms.txt

Use this file to discover all available pages before exploring further.

The MCP Connector lets AI assistants — Claude Desktop, Claude Code, Cursor, ChatGPT, or any client that speaks the Model Context Protocol — read and write your Navis Ops workspace directly. Ask your assistant to plan your week, triage your inbox, draft meeting follow-ups, or scaffold a new project, and it acts against your real data in real time.

Connect your AI client

You have two ways to authenticate: an API key (works with every MCP client, takes under a minute) or OAuth (cleaner for clients that support it, such as Claude Desktop and Cursor).
API key authentication works with every MCP client. You create a token in Navis Ops and paste it into your client’s configuration file.
1

Open Connected Apps

Go to Settings → Connected Apps.
2

Create an API key

Click Create API key. Give it a recognizable name (for example, “Claude Desktop”) and choose a scope:
  • Read — the assistant can query your data but cannot create, update, or delete anything.
  • Read + Write — the assistant can take actions in your workspace.
3

Copy your token immediately

After creation, Navis Ops shows the full token exactly once. It starts with nops_…. Copy it now — you cannot retrieve it later. If you lose it, revoke the key and create a new one.
4

Configure your AI client

In your AI client’s MCP configuration, set the server URL and authorization header:
Server URL:  https://<your-supabase-project>.supabase.co/functions/v1/mcp-server-v2
Header:      Authorization: Bearer nops_<your_token>
The exact format of the configuration file varies by client. Check your client’s documentation for where to add MCP servers.
5

Restart your client

Restart the AI client. Navis Ops tools appear in the assistant’s tool list automatically.
Your API key is shown only once. Store it somewhere safe. If you lose it, go to Settings → Connected Apps, revoke the key, and create a new one.

What the assistant can do

Your connected assistant has access to 52 tools across 12 areas. Read-only tools are available with the Read scope. Tools that create, update, or delete data require the Read + Write scope.
AreaWhat’s available
SearchFull-text search across projects, tasks, notes, calendar events, and links
Workspace metaWho am I, list tags, list folders, list project types, workspace counts
ProjectsCreate, update, delete, set status, pin, unpin, list, get
TasksCreate, update, delete, list, list subtasks, move between projects
NotesCreate, update, delete, list, plus full folder management
CalendarCreate, update, delete, list events
Time trackingRead entries, create, update
GoalsCreate, update, archive, list, get
RoadmapCreate, update, list, get
NotificationsList, mark as read
AnalyticsTime summary, project health, productivity insights
WorkflowsList, get, execute — your assistant can trigger your manual workflows

Resources

The assistant can also read five built-in resources at any time:
  • Workspace summary — a snapshot of your whole workspace
  • All projects — every project you have access to
  • Today’s tasks — tasks due or scheduled for today
  • This week’s calendar — upcoming events for the current week
  • Single project with open tasks — detailed view of one project and its incomplete tasks

Prompt templates

The assistant can invoke four named prompts directly:
PromptWhat it does
plan_my_weekReviews your upcoming tasks and calendar, then drafts a prioritized weekly plan
daily_standupReads yesterday’s completed tasks and today’s agenda, then writes a standup summary
project_kickoffTakes a new project and scaffolds milestones, first tasks, and suggested next steps
task_retrospectiveSummarizes a completed project’s tasks, timelines, and any patterns

Walkthroughs

Daily standup in 30 seconds

You want a formatted standup summary to paste into Slack each morning.
1

Ask your assistant to run the prompt

In Claude Desktop (or any connected client), type:
“Run the daily_standup prompt.”
2

The assistant reads your data

The assistant calls the daily_standup prompt, which reads your tasks completed yesterday, your tasks due today, and your calendar for the day.
3

Copy and paste

The assistant returns a formatted standup (“Yesterday I…, Today I’ll…, Blockers: …”). Edit as needed and paste it into Slack.
You can use plan_my_week the same way on Monday mornings, or project_kickoff immediately after creating a new project.

Triage a meeting transcript into tasks

You’ve just wrapped a meeting and have a transcript. You want action items to appear in Navis Ops without manual entry.
1

Paste the transcript and give an instruction

In ChatGPT (or any connected client), paste the transcript and type:
“Read this transcript and create tasks for the action items, scoped to the Q3 launch project.”
2

The assistant finds your project

The assistant calls list_projects to find the Q3 launch project’s ID.
3

Tasks are created

It calls create_task once per action item, setting the project ID, title, and due date from the transcript.
4

Check Navis Ops

Open your Q3 launch project — the tasks are already there.

Limitations

What you’ll hitWhy
Two scopes only — read and writeThere’s no per-tool access control. The Write scope grants all write tools. You can’t grant “create tasks but not delete projects.”
No rate limit enforced in-appRate limiting relies on Supabase platform limits. Heavy automated workloads can be throttled.
API keys never expire by defaultUnless you set an expiration at creation time, the key works until you revoke it manually.
No live resource updatesResources are fetched on demand. The assistant must re-read a resource to see data that changed since the last read.
You cannot read other users’ dataAll tools are scoped to your authenticated account via row-level security. Cross-user reads are impossible.
API key is shown only onceIf you lose it, revoke the key and create a new one. Navis Ops cannot retrieve it for you.

FAQ

OAuth if your client supports it (Claude Desktop, Cursor). There’s no token to copy, store, or lose — you just approve in the browser. API keys work with every client and are faster to set up the first time.
Yes. Go to Settings → Connected Apps and click Revoke next to the key. The revocation is effective immediately — the next call from that client will fail.
Yes. Go to Settings → Connected Apps, find the client, and click Disconnect. Every active access and refresh token for that session is revoked immediately.
Each connection row in Settings → Connected Apps shows the last-used time. Per-call audit logs are not surfaced in-app yet.
The connection was made with the Read scope only. Create a new API key with Read + Write selected, or — for OAuth — disconnect and reconnect approving the write scope.
No. The bearer token scopes everything to your account via row-level security. The assistant cannot read or act on any other user’s data.
Not at the individual tool level. The only control is Read vs. Read + Write at the connection. If you want the assistant to only read data, use the Read scope.

See also

Workflows

Build automations your assistant can trigger using the Workflows execute tool.

Projects

Understand what the assistant can read and write in your projects.

MCP tools reference

Full reference for all 52 tools, their parameters, and required scopes.

API authentication

API key and OAuth details for developers integrating directly.