Jinike AI MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JINIKE_URL | No | Your Jinike instance URL | https://jinike.ai |
| JINIKE_API_KEY | Yes | Your Jinike API key |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_inboxB | Get recent emails from the user's connected inbox (Gmail or Outlook). Returns sender, subject, date, and preview for each message. |
| send_emailA | Send an email on behalf of the user via their connected email account (Gmail or Outlook). Creates a draft first, then sends it. |
| get_calendarC | Get upcoming calendar events from the user's connected calendar (Google or Outlook). |
| create_eventC | Create a new calendar event in the user's connected calendar. |
| get_tasksA | Get the user's active tasks from Jinike's task management system. Returns tasks sorted by priority and due date. |
| create_taskC | Create a new task in Jinike's task management system. |
| complete_taskC | Mark a task as completed in Jinike's task management system. |
| daily_briefingA | Get a comprehensive daily briefing combining email highlights, calendar events, and task status into a single prioritized overview. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| morning-briefing | Get a comprehensive morning briefing from Jinike |
| email-draft |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| jinike-status | Shows which services are connected to Jinike |
TDQS
Scored across 8 tools
Each tool targets a clear resource+action pair (inbox, email, calendar, tasks), so selection is largely unambiguous. The only mild overlap is daily_briefing, which aggregates the same data as read_inbox/get_calendar/get_tasks, but its composite purpose is described clearly enough to distinguish.
Names follow a mostly predictable verb_noun pattern (send_email, create_event, create_task, complete_task, get_calendar, get_tasks). Minor deviations: 'read_inbox' uses a different fetch verb than 'get_*', and 'daily_briefing' is a noun phrase without a verb.
Eight tools is well-scoped for a personal assistant covering email, calendar, and tasks. Each tool earns its place and no functionality is redundantly split across tools.
Core read/create workflows exist for each domain plus a briefing aggregator, but lifecycle coverage is incomplete: no update/delete for calendar events or tasks, and no reply/archive/search for email. These gaps will force agents to work around missing operations.