MCP Catalogs
Home

agience-core

by Agience·39·Score 45

Agience is an MCP-native platform that structures AI outputs into durable, versioned artifacts with provenance tracking.

ai-llmknowledge-graphdeveloper-tools
16
Forks
1
Open issues
1 mo ago
Last commit
2d ago
Indexed

Overview

Agience operates as an 'operating system for AI workflows', transforming AI-generated outputs into durable, governed knowledge artifacts with identity, provenance, and version history. The platform provides both MCP server capabilities (exposing tools to various clients) and MCP client functionality (consuming other vendor servers). Its architecture includes typed artifact objects, versioned collections, and human-in-the-loop approval gates as first-class operators. The system uses ArangoDB for storage and implements multi-provider OAuth2 authentication with scoped API keys.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

you:Collaborative knowledge management where AI and humans work with the same information substrate
you:Audit trail tracking for AI-generated decisions and content in regulated industries
you:Composable AI agent workflows with structured inputs and outputs via MCP
you:What types of MCP tools does Agience provide?
you:How does Agience handle AI output provenance?

When to choose this

Choose Agience when you need enterprise-grade trust and auditability for AI outputs, with structured artifact tracking and provenance for compliance and collaborative workflows.

When NOT to choose this

Avoid Agience if you need simple file-based storage, prefer permissive licensing over AGPL, or want a lightweight solution without the complexity of its artifact model.

Tools this server exposes

12 tools extracted from the README
  • create_artifact

    Create a new typed artifact with version history

  • query_artifacts

    Search and retrieve artifacts using query language

  • workspace_commit

    Commit workspace artifacts to a collection

  • retrieve_artifact

    Get a specific artifact by its ID

  • update_artifact

    Modify an existing artifact with version tracking

  • create_collection

    Create a new collection for organizing artifacts

  • search_artifacts

    Perform semantic search across artifacts

  • list_workspaces

    List all available workspaces

  • ingest_transcript

    Process a meeting transcript into structured artifacts

  • export_collection

    Export a collection for external use

  • grant_permissions

    Set access permissions for artifacts and collections

  • get_provenance

    Retrieve provenance chain for an artifact

Note: Tools inferred from MCP documentation mentioning '11 tools at /mcp' and architecture descriptions of artifact handling, along with common MCP tool patterns for artifact management systems.

Comparable tools

langflown8ntemporalairflowllama-agents

Installation

Installation Options

**Run at Home (Stable Build)**

# Linux/macOS
curl -fsSL https://get.agience.ai/home/install.sh | sh

# Windows (PowerShell)
irm https://get.agience.ai/home/install.ps1 | iex

**Developer Setup (Build from Source)**

git clone https://github.com/Agience/agience-core.git
cd agience-core
# Linux/macOS
./agience dev -f --build
# Windows
agience dev -f --build

**MCP Client Configuration** For Claude Desktop, add to claude_desktop_config.json:

"mcpServers": {
  "agience": {
    "command": "python",
    "args": ["-m", "agience.mcp"]
  }
}

FAQ

What types of MCP tools does Agience provide?
Agience provides 11 MCP tools focused on artifact management, search, ingestion, reasoning, and output generation, accessible via `/mcp` endpoint.
How does Agience handle AI output provenance?
Agience structures provenance as infrastructure - committed artifacts carry records of what produced them, from what inputs, under whose authority, with this being a fundamental architectural feature rather than an add-on.

Compare agience-core with

GitHub →

Last updated · Auto-generated from public README + GitHub signals.