Personal MCP

io.github.arun250492Published by GitHub account arun250492v2.0.1Updated Nov 20, 2026

Personal desktop assistant + IsItMe? outage triage (DNS, TLS, HTTP, e-mail auth, cloud status).

Overview

AI-generated overview

Local MCP server combining outage triage (DNS, TLS, HTTP, e-mail auth, vendor status) with a personal desktop assistant for files, shell, Gmail and Calendar.

What you can do
  • Diagnose outages and check DNS records, TLS certificates, HTTP responses, e-mail authentication and vendor status pages
  • Inspect the local system: system info, IP addresses, disk usage, port checks and shell commands
  • Manage files and the desktop: list, read, write, search, move and delete files, clipboard, screenshots, open apps and processes
  • Use Gmail and Google Calendar: read the inbox, send mail, view and create events
  • Post to Twitter/X, send notifications and reminders, search and fetch URLs, and use date, calculator and text-to-speech helpers
When to use it
Useful when you troubleshoot whether a site or service is down or only unreachable from your network, and want a verdict with likely cause and next steps. Also suits users who want one local server to let an assistant work with their own machine, files, mail and calendar.
Requirements
Local Python 3.10+ process installed from the personal-mcp-arun package; the MCP Python SDK 2.x is installed automatically. Gmail and Calendar need a Google OAuth desktop client file at ~/.personal-mcp/gmail_credentials.json or the GMAIL_CREDENTIALS_PATH variable, with a browser sign-in on first use. Optional PERSONAL_MCP_CLOUD_URL enables cloud-side comparison; desktop features need the all extras.
Before you install
The default mode registers tools that run shell commands, write, move and delete files, kill processes, send e-mail and post to social media; set PERSONAL_MCP_SAFE_MODE=1 to omit them. Gmail and Calendar access uses a Google OAuth client file stored on disk. The HTTP mode listens on localhost with all tools; only the hosted mode is limited to read-only checks.

Installation

In SourceWeft

  1. Open Personal MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Personal MCP + IsItMe?

An MCP server that does two jobs:

  1. IsItMe? — outage triage for IT people. "Is it down, or is it just me?" One call checks DNS, the TLS certificate, the HTTP response and the hosting provider's status page, then returns a verdict, the likely cause, next steps and a ticket-ready summary. Also available as a ChatGPT app.
  2. Personal desktop assistant. Files, shell, clipboard, screenshots, apps, Gmail, Google Calendar, notifications and more — for Claude Desktop, Claude Code and other local MCP clients.

[IsItMe verdict card]

Install

bash
pip install personal-mcp-arun            # core + IsItMe? triage toolspip install "personal-mcp-arun[all]"     # + Gmail/Calendar, desktop (psutil, clipboard, screenshots), Twitter/X

Python 3.10+. Requires the MCP Python SDK 2.x (installed automatically).

Claude Desktop / Claude Code

json
{  "mcpServers": {    "personal": { "command": "personal-mcp" }  }}

Claude Code: claude mcp add personal -- personal-mcp

IsItMe? triage tools

ToolWhat it does
diagnose(url)One-shot outage diagnosis with a verdict card: DNS + TLS + HTTP + provider status, likely cause, fixes, ticket summary
check_dns(name, record_types)A/AAAA/CNAME/MX/TXT/NS/CAA/SOA from Google + Cloudflare DNS (and your own resolver locally), consistency check
check_tls(url)Certificate expiry, hostname match, issuer, chain trust, protocol
check_http(url)Status, redirect chain, latency, CDN headers, explanations of 5xx / Cloudflare 52x
check_email_auth(domain)MX, SPF (incl. 10-lookup limit), DMARC policy, DKIM under common selectors
vendor_status(vendors)Live status of AWS, Azure, GCP, Cloudflare, GitHub, Slack, Jira, Zoom, Vercel, Netlify, OpenAI, …

Local vs. cloud view. Run locally, the checks run from your network (and can reach internal hosts). Set PERSONAL_MCP_CLOUD_URL=https://<your-hosted-isitme> and call diagnose(url, compare_cloud=true) to also run them from the internet — if it works from the cloud but not from you, the verdict is "your network".

Personal assistant tools

System info, IP addresses, disk usage, port check, shell commands · list/read/write/search/move/delete files · clipboard, screenshots · open URLs, web search, fetch URL · open apps, list/kill processes · Gmail inbox/read/send · Calendar today/upcoming/create · notifications, reminders · Twitter/X post · date/time, calculator, text-to-speech.

Safe mode: set PERSONAL_MCP_SAFE_MODE=1 to not register tools that run commands, write/move/delete files, kill processes, send e-mail or post to social media.

Gmail/Calendar: put a Google OAuth Desktop app client file at ~/.personal-mcp/gmail_credentials.json (or set GMAIL_CREDENTIALS_PATH). The first call opens a browser to sign in.

Run modes

bash
personal-mcp             # stdio (default) — all toolspersonal-mcp --http      # streamable HTTP on 127.0.0.1:8000 — all tools, local clients onlypersonal-mcp --hosted    # public server on 0.0.0.0:$PORT — ONLY the read-only IsItMe? tools

--hosted is what powers the ChatGPT app. It never registers personal tools, only checks public internet addresses on ports 80/443/8080/8443 (private, loopback, link-local and cloud-metadata addresses are refused, and every connection is pinned to a verified IP to stop DNS-rebinding), rate-limits per client, caches results for 60 s and logs no checked URLs. Deploy with the included Dockerfile (see PUBLISHING.md).

Development

bash
pip install -e ".[dev]"pytest -q

Tests spin up local HTTPS servers with valid, expiring, expired, wrong-host and self-signed certificates, and exercise the MCP protocol in-process, over streamable HTTP and over stdio.

License

MIT © Arun

Source: README.md at commit bb3c111

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v2.0.1LatestNov 19, 2026
  2. v1.0.5Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts