Folderr Agent Command & Control Nexus (A-CCN)

A Model Context Protocol (MCP) service endpoint designed to interface with Folderr's backend services, primarily focused on administering and engaging with configured Folderr AI Assistants.

Integration Procedure

Incorporate this definition into your MCP Configuration Block:

{ "mcpServers": { "folderr_nexus": { "command": "npx", "args": ["-y", "@folderr/folderr-mcp-server"] } } }

Core Capabilities

The service exposes the following operational interfaces:

Credential Establishment

Two distinct methodologies for proving identity are supported:

1. Credential-Based Sign-In typescript { "name": "login", "arguments": { "email": "operator@domain.net", "password": "secure-passphrase" } }

2. Token-Based Authorization typescript { "name": "set_api_token", "arguments": { "token": "sec_key_xyz123abc" } }

API access keys should be provisioned via the Folderr Developer Portal. This method is preferable for persistent or automated execution environments.

Agent Lifecycle Management

1. Query Agent Registry typescript { "name": "list_assistants", "arguments": {} }

Retrieves a manifest of all active assistants associated with the authenticated principal.

1. Engage Assistant typescript { "name": "ask_assistant", "arguments": { "assistant_id": "uuid-of-agent", "question": "Provide the requested data point." } }

Dispatches a query payload to a designated agent and awaits the computed reply.

State Persistence

The service persists operational metadata within a local config.json artifact. This includes: - The primary endpoint URL for the Folderr service fabric - The active security credential (derived from login or direct key setting)

Exception Handling

The orchestrator furnishes granular diagnostic feedback for predictable failure modes: - Authorization denial - Malformed request structure - Upstream API service faults - Underlying network connectivity problems

Build Process

To compile the server from source: bash npm install npm run build

Operational Deployment in MCP Context

Integrate using the following structure in your primary configuration file:

{ "mcpServers": { "folderr_nexus": { "command": "node", "args": ["/absolute/path/to/folderr-server/build/index.js"] } } }

Authorization Sequence

1. Execute either the login utility (with credentials) OR the set_api_token utility (with a key).
2. The resulting security credential is automatically cached for subsequent operations.
3. All agent interaction utilities mandate a successful preceding authorization step.

Diagnostic Messages

Key error codes and their implications: - "Not logged in": No security token is currently established. - "Login failed": Credentials validation check failed. - "Failed to list assistants": Issue retrieving the inventory of available agents. - "Failed to ask assistant": Error during query transmission to the target agent.