Skip to main content
Glama
procurement-mailer-mcp

procurement-mailer-mcp

procurement-mailer-mcp

A Model Context Protocol server that lets an SAP Joule agent read and send email from a scoped Microsoft Exchange mailbox. The agent never talks to Microsoft directly β€” this server sits in the middle, translating MCP tool calls into Microsoft Graph requests against a single mailbox.

πŸ“– Setup runbook: https://fairconsult-corp.github.io/procurement-mailer-mcp/ πŸ›οΈ Architecture: https://fairconsult-corp.github.io/procurement-mailer-mcp/architecture.html

Architecture

  SAP Joule Agent  ──▢  procurement-mailer-mcp  ──▢  Exchange / MS Graph
   (BTP / Joule)         (this repo, on CF)          (single scoped mailbox)

Invocation flows left-to-right; data flows back right-to-left. Three stages:

Stage

What it does

1 Β· Joule

Plans the request, picks an MCP tool, calls the server over Streamable HTTP through a BTP destination.

2 Β· MCP (this repo)

Node.js + TypeScript server on Cloud Foundry. Exposes four tools and maps them onto Graph calls through the graph-mail destination (an Entra app identity).

3 Β· Graph

Microsoft Graph over Exchange Online, restricted by an application access policy to just the demo mailbox.

Transport

The server is stateless: every POST /mcp builds a fresh McpServer + StreamableHTTPServerTransport pair (sessionIdGenerator: undefined). GET and DELETE on /mcp β€” the session channels of Streamable HTTP β€” return 405.

Graph access

There is no MSAL or token juggling in code. @sap-cloud-sdk/http-client's executeHttpRequest resolves the graph-mail BTP destination, performs the OAuth client-credentials exchange, and prefixes /v1.0 on every call. The Entra credentials (tenant ID, client ID, client secret) live in that destination, not in environment variables.

Related MCP server: OWA Exchange MCP Server

Project layout

src/
β”œβ”€β”€ index.ts          # Express app + Streamable HTTP transport (POST /mcp)
β”œβ”€β”€ server.ts         # Builds the McpServer, registers `ping`, wires in mail tools
β”œβ”€β”€ tools/
β”‚   └── mail.ts       # The three mail tools: list_messages, read_message, send_mail
└── graph/
    └── client.ts     # graphGet / graphPost via the `graph-mail` destination

manifest.yml          # Cloud Foundry app + service bindings (dest, conn, xsuaa)
index.html            # The setup runbook (published to GitHub Pages)
architecture.html     # Architecture page β€” call flow, components, data model
assets/               # Logo + runbook images

Tools

Tool

Description

Key inputs

ping

Health check β€” returns pong @ <timestamp>.

note?

list_messages

Recent emails from the mailbox: id, subject, sender, received time, read state.

top (1–25, default 10), unreadOnly

read_message

Full body of one email by id.

messageId

send_mail

Send an email from the mailbox.

to, subject, body, contentType (Text/HTML)

Requirements

  • Node.js 22.x (see engines in package.json)

  • For deployment: a SAP BTP subaccount with Cloud Foundry, and the graph-mail destination configured (Entra credentials). See the runbook for the full Microsoft-side and BTP setup.

Run locally

npm install

# Dev β€” tsx watch, hot reload, port 3000 (or $PORT)
npm run dev

# Or build to dist/ and run the compiled server
npm run build
npm start

The server listens on http://localhost:3000/mcp.

Validate with the MCP Inspector

Use a real MCP client β€” not curl, which can't complete the Streamable HTTP handshake.

npx @modelcontextprotocol/inspector
# Transport: Streamable HTTP   URL: http://localhost:3000/mcp
# Connect β†’ List Tools (expect 4) β†’ call `ping` β†’ expect "pong @ <timestamp>"

ping works locally with no extra setup. The three mail tools resolve the graph-mail destination, which only exists on BTP β€” test those against the deployed route, or feed the SAP Cloud SDK a destinations env var when starting the server locally.

Deploy to Cloud Foundry

The app expects three bound services (see manifest.yml): a destination, connectivity, and xsuaa instance.

cf api <CF_API_ENDPOINT>          # e.g. https://api.cf.us10-001.hana.ondemand.com
cf login --sso
cf target -o "<ORG>" -s <SPACE>

# One-time: create the backing services manifest.yml binds
cf create-service destination lite  procurement-mailer-dest
cf create-service connectivity lite procurement-mailer-conn
cf create-service xsuaa application procurement-mailer-uaa

npm run build
cf push

# After re-binding or changing a service: RESTAGE, never restart
cf restage procurement-mailer-mcp

Restage, never restart. Service bindings are only injected into VCAP_SERVICES on cf restage. cf restart reuses the old droplet and the env stays empty.

Configuration

Setting

Where

Notes

MAILBOX

manifest.yml env / src/graph/client.ts default

The mailbox every call targets.

PORT

injected by Cloud Foundry

Defaults to 3000 locally.

Entra credentials

graph-mail BTP destination

Tenant ID, client ID, client secret β€” not env vars.

License

ISC

Tool Schema Changelog

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

Loading tool schema changelog…

    Related MCP Connectors

    • Email infrastructure for AI agents β€” send, receive, search, and reply to email over MCP.

      https://www.primitive.dev/mcp
    • Your agent needs a mailbox of its own β€” to receive, thread, draft and send, with attachments, without borrowing your personal inbox or your company's SMTP. **What you can ask for** β€’ "Create an inbox for this agent and tell me its address." β€’ "Read the new messages in this thread and draft a reply." β€’ "Send this message with the attachment and wait for the response." β€’ "Search this inbox for everything from that domain." β€’ "Show delivery metrics and the events on this inbox." **How to use it** Point any MCP client at https://mcp.aisa.one/mail/mcp and sign in with OAuth β€” there is no key to create or paste. 49 tools: create and delete inboxes, list and read messages, raw message bodies, attachments, threads, drafts and draft attachments, send and reply, message search, inbox events, metrics, and list entries β€” reads and writes. **Why this rather than the source** A real inbox an agent owns, rather than an SMTP credential it borrows from a human. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Find the contact elsewhere in the catalogue, then write to them from here β€” without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/sales/mcp finds the person to write to.

    • Email and optional phone for AI agents: send, receive, search, draft and call over MCP.

      https://agent-api.mailrun.ai/mcp
    • Manage Microsoft 365 email, calendar, contacts and inbox rules via the Graph API with OAuth 2.0.

      https://mcps.work/mcp

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with Microsoft 365 Outlook Mail, allowing email operations via natural language.
      119 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for any Microsoft Exchange / OWA deployment. Gives LLM agents access to email, calendar, directory search, folders, availability, and meeting analytics via 30 tools.
      30
      50 PyPI
      12
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs and MCP clients to read, search, and manage Microsoft Outlook emails through a standardized interface.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables reading, sending, and managing Microsoft 365/Outlook emails through MCP tools with OAuth 2.1 authentication.
      89 npm
      MIT