Skip to main content
Glama
Jinike AI MCP Server

Jinike AI MCP Server

Official
by jinikeai

Jinike AI MCP Server

Connect Claude to your email, calendar, and tasks through Jinike AI.

This MCP server gives Claude direct access to your Jinike-connected services — Gmail, Outlook, Google Calendar, Outlook Calendar, and Task Management — so Claude can read your inbox, schedule meetings, manage tasks, and deliver daily briefings.

Tools

Tool

Description

read_inbox

Get recent emails from Gmail or Outlook

send_email

Send an email through the verification pipeline

get_calendar

Get upcoming calendar events

create_event

Create a calendar event with attendees

get_tasks

Get active tasks sorted by priority

create_task

Create a new task with priority and due date

complete_task

Mark a task as completed

daily_briefing

Get a comprehensive briefing of email, calendar, and tasks

Related MCP server: ClaudePost

Prompts

Prompt

Description

morning-briefing

Comprehensive morning briefing template

email-draft

Draft an email with voice calibration

Installation

Claude Code

git clone https://github.com/jinikeai/jinike-mcp-server.git
cd jinike-mcp-server
npm install
npm run build

Add to your Claude Code config:

{
  "mcpServers": {
    "jinike": {
      "command": "node",
      "args": ["/path/to/jinike-mcp-server/build/index.js"],
      "env": {
        "JINIKE_URL": "https://jinike.ai",
        "JINIKE_API_KEY": "your-api-key"
      }
    }
  }
}

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "jinike": {
      "command": "node",
      "args": ["/path/to/jinike-mcp-server/build/index.js"],
      "env": {
        "JINIKE_URL": "https://jinike.ai",
        "JINIKE_API_KEY": "your-api-key"
      }
    }
  }
}

Configuration

Variable

Description

Default

JINIKE_URL

Your Jinike instance URL

https://jinike.ai

JINIKE_API_KEY

Your Jinike API key

Required

Get your API key from jinike.ai in the Settings tab.

Requirements

  • Node.js 18+

  • A Jinike AI account with email and/or calendar connected

  • Jinike API key

How It Works

The MCP server acts as a bridge between Claude and your Jinike account:

  1. Claude invokes a tool (e.g., read_inbox)

  2. The MCP server calls Jinike's API with your credentials

  3. Jinike fetches data from your connected services (Gmail, Outlook, etc.)

  4. The response flows back to Claude

  5. Email sending goes through Jinike's verification pipeline for safety

All actions respect Jinike's Hallucination Defense System (HDS) and verification pipeline. High-risk actions (sending emails, deleting events) require approval.

Security

  • Your API key authenticates you with Jinike

  • Email data is not stored by the MCP server

  • All email sending goes through Jinike's approval flow

  • The MCP server runs locally on your machine (stdio transport)

About Jinike AI

Jinike is a personal AI life operating system with 55 capabilities across 9 pillars. Gmail, Outlook, Google Calendar, Slack, LinkedIn, X/Twitter, Instagram integrations deployed. Patent-pending Hallucination Defense System. Jinike AI, LLC.

Website: jinike.ai

License

MIT

Available Tools

8 tools
complete_taskC

Mark a task as completed in Jinike's task management system.

Inputs: taskId (required).

create_eventC

Create a new calendar event in the user's connected calendar.

Inputs: title (required), startTime (required), endTime, location, +2 more.

create_taskC

Create a new task in Jinike's task management system.

Inputs: title (required), dueDate, priority, description.

daily_briefingA

Get a comprehensive daily briefing combining email highlights, calendar events, and task status into a single prioritized overview.

Inputs: no named parameters.

get_calendarC

Get upcoming calendar events from the user's connected calendar (Google or Outlook).

Inputs: daysAhead.

get_tasksA

Get the user's active tasks from Jinike's task management system. Returns tasks sorted by priority and due date.

Inputs: status, priority.

read_inboxB

Get recent emails from the user's connected inbox (Gmail or Outlook). Returns sender, subject, date, and preview for each message.

Inputs: maxResults, unreadOnly.

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.

Inputs: to (required), body (required), subject (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 8 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers