Arcanna Input MCP Server
# Arcanna Input MCP Server
The Arcanna Input MCP server allows user to interact with Arcanna's AI use cases that use external api integration through the Model Context Protocol (MCP).
## Usage with Claude Desktop or other MCP Clients
#### Configuration
Add the following entry to the `mcpServers` section in your MCP client config file (`claude_desktop_config.json` for Claude
Desktop).
### Use docker image (https://hub.docker.com/r/arcanna/arcanna-input-mcp-server) or PyPi package (https://pypi.org/project/arcanna-mcp-input-server)
### Building local image from this repository
#### Prerequisites
- Docker - https://docs.docker.com/engine/install/
#### Configuration
1. Change directory to the directory where the Dockerfile is.
2. Run ```docker build -t arcanna/arcanna-input-mcp-server . --progress=plain --no-cache```
3. Add the configuration bellow to your claude desktop/mcp client config.
```json
{
"mcpServers": {
"arcanna-input-mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"ARCANNA_INPUT_API_KEY",
"-e",
"ARCANNA_HOST",
"-e",
"ARCANNA_USER",
"arcanna/arcanna-input-mcp-server"
],
"env": {
"ARCANNA_INPUT_API_KEY": "<YOUR_ARCANNA_API_KEY_HERE>",
"ARCANNA_HOST": "<YOUR_ARCANNA_HOST_HERE>",
"ARCANNA_USER": "<YOUR_USERNAME_HERE>"
}
}
}
}
```
## Features
- **Job Management**: Create, retrieve, start, stop, and train jobs
- **Event Processing**: Send events for AI-powered decision making
- **Feedback System**: Provide feedback on decisions to improve model accuracy
- **Health Monitoring**: Check server and API key status
## Tools
### Job Management
- **get_external_input_jobs**
- Retrieve all jobs associated with your API key
- Returns a list of job details including status, labels, and processing metrics
- **get_external_input_job_by_id**
- Retrieve specific job details by ID
- **get_external_input_job_by_name**
- Retrieve specific job details by name
- **get_external_input_job_labels**
- Retrieve decision labels for a specific job
### Event Management
- **send_event_to_external_input_job**
- Submit an event to Arcanna for AI decision-making
- **send_event_with_id_to_external_input_job**
- Submit an event with a custom identifier
### System Health
- **health_check_input_server**
- Verify server status and API key validity
- Returns API key authorization status
TDQS
Scored across 4 tools
Tools are mostly distinct: listing jobs, health check, and two event-sending variants. The two send tools are similar but clearly differentiated by the presence of an optional event_id. Some potential for confusion but descriptions clarify.
Names use snake_case but patterns vary: 'get_external_input_jobs' is verb_noun, 'health_check_input_server' is noun_verb_noun, while the send tools follow verb_noun_prep_noun. Inconsistent use of singular/plural ('jobs' vs 'job').
Four tools are well-scoped for an input server: one to list available jobs, one for health check, and two for sending events (with/without custom ID). No unnecessary tools.
Covers core operations: listing jobs, health check, and event ingestion. Missing functionality like retrieving event status or updating/deleting events, but these may be out of scope for an input-focused server.