agience-core
by Agience·★ 39·Score 45
Agience is an MCP-native platform that structures AI outputs into durable, versioned artifacts with provenance tracking.
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:
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 READMEcreate_artifactCreate a new typed artifact with version history
query_artifactsSearch and retrieve artifacts using query language
workspace_commitCommit workspace artifacts to a collection
retrieve_artifactGet a specific artifact by its ID
update_artifactModify an existing artifact with version tracking
create_collectionCreate a new collection for organizing artifacts
search_artifactsPerform semantic search across artifacts
list_workspacesList all available workspaces
ingest_transcriptProcess a meeting transcript into structured artifacts
export_collectionExport a collection for external use
grant_permissionsSet access permissions for artifacts and collections
get_provenanceRetrieve 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
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
Last updated · Auto-generated from public README + GitHub signals.