advocatehub-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP server (default 8787). | |
| INFLUITIVE_BASE_URL | No | Base URL for the Influitive API (e.g., https://api.influitives.com for staging, https://api.influitive.com for production). Default is likely staging. | |
| MCP_HTTP_BEARER_MAP | No | Required for HTTP mode: a bearer token and org ID in format 'token:orgId'. |
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_advocatehub_toolsA | Returns the complete catalog of AdvocateHub MCP tools with names and descriptions. Use this to discover, search, find, or list every available tool when tool_search only shows a subset. Filter by keyword (e.g. "member", "search", "reward", "challenge") or credential scope. No tenant credentials required. |
| configure_tenantA | Supplies org-wide API credentials (api_token + org_id) and/or hub_url for SSO. Required before other tools when the server started unconfigured. Org-token tools need api_token + org_id; SSO-only sessions need only hub_url (org id is derived from the JWT after sso_login). |
| get_active_identity_contextA | Reports which credentials are active in this MCP session: org-wide API token (when configured) and individual-user SSO (when hub_url is set or after sso_login). Call before choosing org-token admin tools vs my_* / SSO self-service tools. |
| audit_tailA | Return the last N executed write audit entries for this tenant from ~/.advocatehub-mcp/audit/-YYYY-MM.jsonl (and legacy .jsonl if present). Only confirm:true writes are logged; previews are excluded. |
| audit_searchA | Search executed write audit entries for this tenant. Filter by tool name, actor type (org_token or sso), and optional ISO date range. Reads ~/.advocatehub-mcp/audit/-YYYY-MM.jsonl (and legacy .jsonl). |
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
The tools are mostly distinct: list_advocatehub_tools for discovery, configure_tenant for setup, get_active_identity_context for session context. The only potential confusion is between audit_tail and audit_search, but they are differentiated by recency vs. filtered search, and the descriptions clarify the distinction.
All tool names use snake_case and are readable. Most follow a verb_first pattern (list_, configure_, get_), but audit_tail and audit_search place the resource (audit) before the verb, a minor deviation from the otherwise consistent convention.
With five tools, the count falls within the typical 3-15 range and feels reasonable for a utility/admin-focused server. It is slightly on the smaller side given the apparent domain, but not inappropriately sparse.
The server name and list_advocatehub_tools description reference domain objects like members, rewards, and challenges, yet none of the actual tools perform any domain operations. The set is limited to configuration, identity, and audit utilities, leaving the core AdvocateHub functionality completely absent. Even within the meta-purpose, there is no way to modify configuration or manage audit logs beyond reading them.