general

Project rules for an Outlook MCP server, including JavaScript module style, shared configuration, response formatting, authentication errors, and diagnostic logging. An MCP server connects an AI tool to external data or actions.

In plain words
What is it for?
Use it when adding or changing Outlook MCP server code, especially handlers, configuration, response formatting, authentication handling, and logs.
Why use it?
It gives contributors consistent patterns for writing handlers and returning errors and data without breaking the server protocol.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/titanzero/outlook-mcp/general
Clone the repo
git clone --depth 1 https://github.com/titanzero/outlook-mcp

Made for: Cursor.

Per session 211 This file is loaded in full into every session.
When invoked 211 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin fork From a forked repository.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00211 $0.00211
Opus 5 $0.00105 $0.00105
Sonnet 5 $0.00042 $0.00042
Haiku 4.5 $0.00021 $0.00021

Measured yesterday against content hash 2876181dad40, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

general scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/general.mdc · 27 lines

What it actually says

Core Conventions

  • Use CommonJS (require / module.exports) in plain JavaScript; do not use ESM.
  • Keep shared constants in config.js; avoid hard-coded field lists, pagination, URLs, and timezone values.
  • Build MCP responses with makeResponse() and makeErrorResponse() from utils/response-helpers.js.
  • Detect auth failures with isAuthError(error) and return the auth message directly.
  • For data output, call formatResponse(structuredData, textFallback) from utils/response-formatter.js.
  • Log diagnostics with console.error() (stdout is reserved for MCP protocol traffic).

Baseline Error Pattern

try {
  // handler logic
} catch (error) {
  if (isAuthError(error)) {
    return makeErrorResponse(error.message);
  }
  return makeErrorResponse(`Error doing X: ${error.message}`);
}
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 27 lines · 211 tokens per session scan A 2876181dad40

Subscribe to this mod's changes

general is a cursor rule published in the GitHub repository titanzero/outlook-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 211 tokens to every session, about $0.0011 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.