Simosphere Ai · Governed Access For Microsoft 365

Created By
SIMO GmbHa day ago
AI Governance Infrastructure for Microsoft 365. 24 MCP tools with policy enforcement, Need-to-Know compliance filter, revision-safe audit trail, and per-resource scope control. Deployed in your own Azure tenant — your data never leaves. DSGVO-first, EU AI Act ready.
Overview

SIMOSphere AI · Governed Access Platform for Microsoft 365

AI Governance Infrastructure that gives your organization control over what AI agents can see in your Microsoft 365 — deployed in your own Azure tenant.

24 MCP Tools

Calendar: list, create, findMeetingTimes, freeBusy Files: list, search People: search, myManager SharePoint: metadata, lists, items, search, drive (list/read/upload/share), pages

Five Governance Layers

  1. M365 Secure Connector — 24 Microsoft Graph tools, each call audited
  2. MCP Context Gateway — per-resource scope control, tenant isolation
  3. Policy & Filter Engine — keyword, regex, DLP, Need-to-Know redaction
  4. AI Heuristics Engine — automatic PII, legal risk, fraud detection
  5. Audit & Review Layer — complete prompt history, regulatory exports

For Regulated Industries

Banking (BaFin, DORA) · Insurance (VAIT) · Pharma (GxP) · Legal · Critical Infrastructure (NIS2)

What Separates Us from Microsoft Copilot

  • Model-agnostic (MCP-native, not locked to Microsoft)
  • EU sovereign (Azure West Europe, your own tenant)
  • Full audit trail (not a blackbox)
  • Per-resource access control (not all-or-nothing)
  • AI Act ready, DSGVO-first

Server Config

{
  "mcpServers": {
    "simosphere-m365": {
      "url": "https://m365.simosphereai.com/mcp/v1",
      "transport": "streamable-http",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}
Project Info
Created At
a day ago
Updated At
a day ago
Author Name
SIMO GmbH
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Thousand Api

14 hours ago
Hellogrowthcrm

2 days ago
GovQL
@Alex Stout

# govql-mcp-server An MCP (Model Context Protocol) server for [GovQL](https://govql.us) — gives AI clients like Claude Desktop, Claude Code, and Cursor direct access to the US Congressional GraphQL API at [api.govql.us/graphql](https://api.govql.us/graphql) without bespoke HTTP wiring. For the design rationale (why FastMCP-Python, the passthrough+curated philosophy, roadmap through v0.4), see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md). ## What you can do with it Ask an agent questions like: - *"How did Vermont's two senators vote on the most recent nomination?"* - *"Which legislators in the 118th Congress switched parties during their service?"* - *"Compare Senator Sanders' voting record to Senator Murkowski's on cloture votes in the most recent Congress."* The agent picks the right tool, writes the GraphQL query against the live schema, and parses the response — no manual API wrangling. ## Install The server runs as a per-client subprocess over stdio. Pick your client: ### Claude Desktop Edit `claude_desktop_config.json` (Settings → Developer → Edit Config): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` Restart Claude Desktop. The `govql` tools appear in the tools panel. ### Claude Code Add to `.mcp.json` in your project (or `~/.mcp.json` for global): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` ### Cursor Settings → MCP → Add Server. Use the same `command` / `args` as above. ### Other clients Any MCP-compatible client that supports stdio servers will work. The command is `uvx govql-mcp-server` with no required arguments. ## Tools | Tool | Purpose | |---|---| | `execute_graphql` | Run any GraphQL query against the GovQL endpoint. Returns the result plus an `last_ingest` timestamp so the agent can reason about data freshness. | | `list_types` | Returns the names and kinds of every type in the GovQL schema. Optional `kind` filter (`"OBJECT"`, `"INPUT_OBJECT"`, `"ENUM"`, etc.) to narrow further. Start here when you don't know what's queryable. | | `describe_type` | Returns one type's full details — fields, arg signatures, input fields, enum values. Call after `list_types` to learn the shape of a specific type before writing a query. | ## Configuration All env vars are optional — the package is zero-config for end users. | Env var | Default | Purpose | |---|---|---| | `GOVQL_ENDPOINT` | `https://api.govql.us/graphql` | Endpoint to query. Override to point at a local dev stack. | | `GOVQL_TIMEOUT_MS` | `30000` | Per-request HTTP timeout. | | `LOG_LEVEL` | `INFO` | Logging level. Logs go to stderr only (stdout is reserved for the MCP transport). | ## Limits (enforced by the upstream API) - Max query depth: 10 - Max query complexity: ~10 billion points (`first: N` multiplies child cost by N — keep page sizes reasonable on deeply nested queries) - Rate limit: 100 requests / 60 s per source IP A depth or complexity violation surfaces as a GraphQL `errors` entry in the tool response so the agent can adjust and retry. ## Data freshness Every `execute_graphql` response includes a `last_ingest` ISO timestamp. Vote data refreshes hourly; legislator data refreshes daily. ## Status Version 0.1.0 ships three foundational tools: a GraphQL passthrough (`execute_graphql`) and two narrow schema-discovery tools (`list_types`, `describe_type`). Curated higher-level tools (`find_legislator`, `get_voting_record`, `compare_voters`, etc.) are planned for subsequent releases — see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md) for the roadmap. ## Links - [GovQL project site](https://govql.us) - [GraphQL API](https://api.govql.us/graphql) - [Source / issues](https://github.com/govql/govql)

2 days ago