eight-mcp-community
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EIGHT_EMAIL | No | Email for password login (requires EIGHT_PASSWORD) | |
| EIGHT_COOKIE | No | Cookie header for authentication | |
| EIGHT_PASSWORD | No | Password for email login (requires EIGHT_EMAIL) | |
| EIGHT_COOKIE_FILE | No | Mozilla/Netscape cookie jar path | |
| EIGHT_SESSION_COOKIE | No | Alternate Cookie header | |
| EIGHT_MCP_COMMUNITY_CONFIG | No | Path to config JSON with a cookie field |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| eight_auth_statusA | Check whether Eight authentication is configured and currently usable. |
| eight_auth_loginB | Run CLI browser login in a subprocess, capture Eight cookies, and save them. |
| eight_set_cookieC | Store a Cookie header in the local MCP config file. |
| eight_search_personC | Search registered Eight cards by default; source='all' also includes public network. |
| eight_fetch_personA | Fetch detailed contact/profile fields for an id returned by eight_search_person. |
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 5 tools
Each tool has a distinct purpose: authentication operations (login, status, cookie management) are separate from data retrieval (search, fetch). No overlap or ambiguity.
All tools follow the consistent pattern 'eight_verb_noun' (e.g., auth_login, fetch_person). No mixing of conventions or vague verbs.
5 tools is a compact but complete set for authentication and basic contact retrieval. Not bloated or insufficient.
Covers authentication and read operations (search, fetch) well, but lacks write operations like create/update/delete person. Minor gap for a contact management domain.