Narla MCP Connector
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | HTTP only. Bind address. | |
| PORT | No | HTTP only. Port to listen on. | |
| NARLA_DEMO | No | Set to 1 to run the in-memory demo without Notion. | |
| NARLA_SCOPES | No | stdio only. Scopes for local mode. | read,write |
| NARLA_TOKENS | No | HTTP only. token:scopes pairs separated by ;. Tokens must be 32+ characters. | |
| NOTION_TOKEN | No | Notion integration token. Required unless NARLA_DEMO=1. | |
| ALLOWED_HOSTS | No | HTTP only. Allowed Host headers. | |
| NARLA_TASK_PREFIX | No | Task numbering prefix, e.g. NARLA-TASK gives NARLA-TASK-12: ... | |
| NARLA_DEFAULT_MODEL | No | Value for the queue's Model select on new tasks. | |
| NARLA_MEMORY_PAGE_ID | No | Notion page with the business memory. | |
| NARLA_QUEUE_DATA_SOURCE_ID | No | Data source id of the task queue. Required unless NARLA_DEMO=1. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_agentsA | Lists the Narla agents installed for this company and what each one does. |
| list_tasksA | 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). |
| get_taskA | Returns one task: its instructions, its status and the report the agent wrote (what it did and what it changed). |
| read_business_memoryA | Returns the company's business memory, the single source of truth every agent reads: brand kit, services, prices, opening hours and approved answers. |
| create_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. |
| cancel_taskA | Marks a Draft task as Voided, so it never runs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.