MCP Server and Accessnew · 1.6

Anxeb Terminal runs an MCP server on the machine (off by default; Settings, MCP). Its tools reach projects, tasks, comments, agents, AI sessions, terminals, remote hosts and their files, notifications and the log: about seventy, each marked as reading, changing, acting outside or deleting. Clients connect with a token made for each one, shown once, and revoked from the same tab; the sessions of projects and the agents get theirs from the app.

What a client may do is said by access tables: by resource (projects, tasks, notes, assets, comments, hosts…) and right (read, create, update, delete). A project says it for its supervisor and its specialists, each agent for itself, each task for its specialist; a cell left empty takes the word of the layer under it. Actions that reach outside the app can ask first, in a dialog.

No tool ever gives or takes a secret: passwords and keys stay in the app.

What it does

• A local MCP server with about seventy tools.
• Tokens per client, shown once, revocable.
• Layered access tables per project, agent and task.
• Confirmation for actions outside the app.
• No secrets through MCP.

How it behaves

• The session of a project can be kept from changing tasks (Settings, MCP).

Why it matters

• Your AI tools see your servers and backlog, and only what you allow.