Narla MCP Connector
Uses a Notion database as the task queue and optionally a Notion page for business memory. Provides tools to list tasks and agents, get task details and reports, create draft tasks, cancel draft tasks, approve tasks, and read the company's business memory.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Narla MCP Connector draft a task for Narla Marketing to post our new product"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Narla MCP connector
Work with your Narla AI agents from the assistant you already have open: ChatGPT, Claude or Cursor.
Narla installs AI agents inside a company: Narla Marketing (edits photos and video, writes and publishes posts, keeps the website and online shop up to date), Narla Ops (company systems and documents) and Narla Voice (answers customers by phone and WhatsApp). The team directs them in plain language. This connector, built on the open Model Context Protocol, lets the team do that from any MCP-capable assistant.
What it does
Tool | Scope | What it does |
| read | The agents installed for the company and what each one does |
| read | Recent tasks and their status, newest first |
| read | One task: its instructions, its status and the agent's report (what it did and what it changed) |
| read | The company's single source of truth: brand kit, services, prices, hours |
| write | Gives an agent a task in plain language. Saved as Draft: nothing runs yet |
| write | Voids a Draft task |
| approve | Approves a Draft task so the agent starts it. Requires |
Nothing runs without a person's approval. Every task starts as a Draft, and every finished task keeps a report. Narla Voice takes no instructions from staff; changes to it go through Narla Ops.
Tasks live in a Notion database (the queue the agents read). The connector only touches pages inside that one queue.
Related MCP server: Forja MCP Server
Quick start
npm install
npm run build
NARLA_DEMO=1 NARLA_TOKENS="$(openssl rand -hex 32):read,write" npm start # in-memory demo, no NotionWith Notion, copy .env.example, fill in a Notion integration token that has access only to the task queue (and, optionally, the business memory page), and start the server.
Connect your assistant
Cursor (local, no server needed)
Clone this repository, run npm install && npm run build, then add to ~/.cursor/mcp.json:
{
"mcpServers": {
"narla": {
"command": "node",
"args": ["/path/to/narla-mcp/dist/stdio.js"],
"env": {
"NOTION_TOKEN": "secret_xxx",
"NARLA_QUEUE_DATA_SOURCE_ID": "your-data-source-id",
"NARLA_TASK_PREFIX": "NARLA-TASK",
"NARLA_SCOPES": "read,write"
}
}
}
}Cursor can also use the remote server: "url": "https://your-host/mcp" with header Authorization: Bearer <token>.
ChatGPT and Claude (remote)
Deploy the HTTP server (any Node 20+ host). In the assistant's custom connector settings, add:
https://your-host/mcp/<your-token>The token in the path is for apps whose connector settings take only a URL. Treat that URL as a password. Clients that support headers should use Authorization: Bearer <token> with https://your-host/mcp instead.
Claude Desktop (local)
Same as Cursor, in claude_desktop_config.json.
Configuration
Variable | Required | Meaning |
| yes, unless | Notion integration token |
| yes | Data source id of the task queue |
| no | Task numbering prefix, e.g. |
| no | Notion page with the business memory |
| no | Value for the queue's |
| HTTP only |
|
| stdio only | Scopes for local mode. Default |
| HTTP only | Bind address and allowed |
The queue is expected to have these properties: Title (title), Status (select with Draft, Approved, Running, Done, Failed, Voided), Tier (select: Low, Medium, High), Result (text, written by the agent), and optionally Model (select).
Security
Give each person their own token, with the smallest scope they need. Only the owner should have
approve.Tokens are held in memory only as SHA-256 hashes and compared in constant time.
The Notion integration should be shared with the queue and the memory page only. The connector refuses any page outside the configured queue.
The HTTP server is stateless and keeps no conversation data.
OAuth is on the roadmap; until then, rotate a token by changing
NARLA_TOKENSand restarting.
Found a security issue? Write to contact@narla.digital rather than opening a public issue.
Development
npm test # vitest: tools, scopes, HTTP auth, Notion store
npm run dev # HTTP server with tsxLicense
Apache License 2.0. Copyright 2026 NARLA S.R.L.
Available Tools
6 toolscancel_taskCancel a task that has not startedADestructiveIdempotent
Marks a Draft task as Voided, so it never runs.
Inputs: task_id (required).
create_taskGive an agent a taskA
Creates a task for one agent, in plain language. The task is saved as a Draft and does not run until a person approves it. Narla Voice does not take tasks; send changes for it to Narla Ops.
Inputs: agent (required), title (required), instructions (required), tier.
get_taskRead a task and its reportARead-only
Returns one task: its instructions, its status and the report the agent wrote (what it did and what it changed).
Inputs: task_id (required).
list_agentsList the company's agentsARead-only
Lists the Narla agents installed for this company and what each one does.
Inputs: no named parameters.
list_tasksList tasksARead-only
Lists the most recent tasks, newest first, with their status. Filter by status to see, for example, what is waiting for approval (Draft) or what is finished (Done).
Inputs: limit, status.
read_business_memoryRead the business memoryARead-only
Returns the company's business memory, the single source of truth every agent reads: brand kit, services, prices, opening hours and approved answers.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool targets a distinct resource and action: list_agents (agents), list_tasks/get_task (tasks at collection vs single level), read_business_memory (memory), and create_task/cancel_task (distinct mutations). There is no overlap that would cause misselection.
All six tools follow a clean verb_noun pattern (list_agents, list_tasks, get_task, read_business_memory, create_task, cancel_task) in consistent snake_case. Minor get/read variation is idiomatic and predictable.
Six tools is well-scoped for an agent/task connector: enough to cover discovery, inspection, creation, and cancellation without bloat.
The task surface has create, list, get, and cancel, but no update tool and no approve tool, even though the workflow explicitly depends on a person approving Drafts before they run. Agents hit a dead end after creating a task, unable to approve or edit it.
Maintenance
Related MCP Connectors
Task management your AI agents can actually run. One line becomes a context-ready task over MCP.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
Build and run AI workflows, agents, data tables and 1000+ API integrations from any MCP client.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceBring BasicOps into your AI assistant. With MCP, your assistant can read your workspace, turn chat into structured tasks, and keep projects moving by updating owners, due dates, and status as decisions happen. BasicOps keeps humans and agents aligned in one place—tasks, messages, and projects—so work doesn’t get lost across tools. All actions respect your BasicOps access controls.1-
- AlicenseNot gradedqualityBmaintenanceExposes specialized agents as MCP tools so users can manage and triage Jira tasks, analyze repositories for health and conventions, generate commit/PR/DevOps patterns, assemble reports, produce slides and infographics, and run semantic search over a knowledge base. Everything is invokable directly from inside a coding session in Claude Code, Cursor, or Claude Desktop.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents such as ChatGPT, Claude, and local LLMs to operate an enterprise digital-operations platform through MCP, exposing 19 model tools and 3 app-only tools for identity, data, workflow, files, and PII-controlled operations with role-based permissions and two-phase confirmations.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude, Cursor, VS Code, and Windsurf to manage workspaces, projects, tasks, and AI agents through natural language.2,530 npmMIT