npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

office-politics-mcp

v1.0.0

Published

Funny MCP server that decodes office politics, meeting danger, and diplomatic workplace replies

Downloads

136

Readme

Office Politics MCP

A funny MCP server that treats workplace ambiguity like a high-stakes diplomatic incident.

It helps AI assistants:

  • decode vague office phrases
  • assess meeting danger
  • generate politically safe replies
  • read local office-politics skill guides

Tools

  • decode_office_signal Interprets vague workplace messages, feedback, and managerial phrases.
  • meeting_risk_assessment Estimates whether a meeting is useful, hazardous, or ceremonial time loss.
  • career_damage_control Drafts diplomatic replies for awkward workplace situations.
  • office_guide Returns the internal skill guides used by the MCP.

Skills

The package ships with these local skill files under office_skills/:

  • corporate_dictionary.md
  • meeting_survival.md
  • feedback_politics.md
  • response_playbook.md

Requirements

  • Node.js 18+
  • npm / npx available on the machine

Local Run

npm install
npm start

For remote mode:

npm run start:remote

MCP Config

Use via npx after publishing:

{
  "servers": {
    "office-politics": {
      "command": "npx",
      "args": ["-y", "office-politics-mcp"]
    }
  }
}

For local development before publishing:

{
  "servers": {
    "office-politics": {
      "command": "node",
      "args": ["/absolute/path/to/Office_Politics_MCP/server.js"]
    }
  }
}

Example Prompts

  • What does "let's take this offline" really mean?
  • Decode this message: "Interesting idea, let's revisit next quarter."
  • Assess this meeting: title "Quick Alignment", 11 attendees, no agenda, director organizer, 60 minutes.
  • Help me reply professionally to an urgent weekend request.
  • Show me the corporate dictionary guide.
  • Decode this feedback: "Great job, keep doing what you're doing."
  • Tell me whether this meeting is dangerous: "Touch Base", 9 people, no agenda.
  • Give me a diplomatic pushback reply for an 8:30 PM request.

Remote Mode

server-remote.js starts HTTP/SSE endpoints for remote MCP hosting:

PORT=3100 npm run start:remote

Package Notes

This package depends on the bundled office_skills markdown files at runtime. The files list in package.json ensures those guides are included when publishing to npm.

Publish Checklist

  1. Run npm pack and inspect the tarball contents.
  2. Confirm office_skills/*.md is included.
  3. Test the packed artifact in a clean folder.
  4. Publish with npm publish or npm publish --access public if using a public scope.