Skip to main content
Glama
Sign In
mcp-multisource

mcp-multisource

by arpitpaliwal007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-multisource

No user-submitted related servers found.

    Related Servers

    • Nexus

      indraxneel
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables models to query enterprise systems—structured data, live GitHub REST API, and unstructured document embeddings—through a single, per-caller scoped MCP tool surface with task-shaped tools and recovery-aware errors.
      90 npm
      ISC

    • Notion MCP Server

      gerhardsharma728
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents and MCP clients to read and write a Notion workspace through a single token, covering pages, databases, blocks, comments, templates, and file uploads. It keeps the model's context small by exposing three tools and fetching operation schemas on demand, while supporting batched, idempotent mutations and headless use in CI or self-hosted deployments.
      5,643 npm
      MIT

    • Tacit

      PhaseYon
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude and Cursor to search a team's synced Slack, GitHub and Notion content through permission-aware hybrid search with citations, retrieve a source document with its review and comment thread, and query time-aware knowledge graph facts when the graph is enabled. Every tool call runs with the signed-in user's permissions, so the assistant sees exactly what that user can see.
      11 npm
      Apache 2.0

    • MonoPulse MCP Engine

      Ravikishore710
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables an event-driven operations agent to query internal SQL, GitHub, Slack, Jira, documentation, and Kubernetes telemetry through 28 RBAC-gated MCP tools, with shared memory for playbook retrieval and incident workflows.
      MIT
    • One

      Oneofficial

      withoneai
      A
      license
      A
      quality
      A
      maintenance
      Search, document and execute authenticated API calls across all your apps (Gmail, Slack, Stripe, Notion, GitHub, and more) through 4 universal tools whose context footprint stays constant no matter how many connections you add. Hosted remote server with OAuth at https://mcp.withone.ai/mcp, or run locally via npx @withone/mcp.
      3
      996 npm
      12
      MIT

    • Notion MCP Server

      George91171
      A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI agents and coding assistants read/write access to Notion — creating and editing pages, querying databases, appending blocks, applying templates, commenting, and uploading files — through just three context-efficient tools. It authenticates with a single token so it works headless in automation, CI, and self-hosted deployments, with batched mutations, idempotency keys, and retry handling built in.
      5,643 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool addresses a completely distinct concern: release_readiness provides aggregated cross-source data, system_health reports on source connectivity/status, and access_policy describes permissions. There is no overlap or ambiguity between their purposes.

    Naming Consistency5/5

    All tool names follow the same snake_case noun_noun pattern (release_readiness, system_health, access_policy), which is predictable and readable. No mixed conventions or vague verbs appear.

    Tool Count5/5

    Three tools is a well-scoped count for a focused multisource status server. Each tool earns its place and the set feels neither bloated nor too thin.

    Completeness4/5

    The server covers the core lifecycle of reading cross-source release readiness, monitoring source health, and checking access. A minor gap is the lack of a tool to query a specific source in detail or perform any mutating action, but agents can work around this with release_readiness and system_health.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Resources