How do I use Arkiv MCP Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Arkiv MCP Server find all posts with score > 10 on Arkiv" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

de en es ja ko ru zh

Arkiv MCP Server

by arrivets

Overview Schema Related Servers Score Discussions

JavaScript

Remote

Arkiv MCP Server

A Model Context Protocol (MCP) server that exposes Arkiv database chain querying capabilities to AI agents and applications.

Quick Start

1. Build

cd arkiv-mcp
npm install
npm run build

2. Add to Claude Code

Run this from the arkiv-mcp directory:

claude mcp add arkiv -- node $(pwd)/dist/index.js

Or add it manually to ~/.claude/settings.json:

{
  "mcpServers": {
    "arkiv": {
      "command": "node",
      "args": ["/absolute/path/to/arkiv-mcp/dist/index.js"]
    }
  }
}

For Claude Desktop, add the same block to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows).

3. Query the Kaolin testnet

Once connected, the query_entities tool is available. Example prompts:

"Query all entities on Arkiv"
"Find all Arkiv entities where type = "post" and score > 10"
"Show me entities owned by 0x1234... on the Arkiv testnet"
"Get the first 5 entities matching status = "active", then paginate"

Related MCP server: TextQL MCP Server

Features

Query entities from Arkiv database chains using a SQL-like filter expression
Full arkiv_query syntax: comparisons, logical operators, glob matching, synthetic attributes
Pagination support with cursor
Configurable return fields (attributes, metadata, payload)
Defaults to Kaolin testnet

Installation

cd arkiv-mcp
npm install
npm run build

# Or use tsx for development
npm run dev

Usage

Start the server

# Using default Kaolin testnet
npm start

# With custom node URL
npm start -- --node-url https://your-arkiv-node.rpc

# Or with tsx for development
npm run dev -- --node-url https://your-arkiv-node.rpc

Environment Variables

Variable	Description	Required
`ARKIV_NODE_URL`	Arkiv node RPC URL	No (defaults to Kaolin testnet)

Command Line Options

Option	Description	Default
`--node-url <url>`	Arkiv node RPC URL	Kaolin testnet
`--help`, `-h`	Show help	-

MCP Tool

`query_entities`

Query entities from an Arkiv database chain.

Parameters

Parameter	Type	Description	Default
`filter`	string	Filter expression (see syntax below)	`$all`
`limit`	number	Maximum number of entities to return (max 200)	-
`cursor`	string	Pagination cursor from a previous response	-
`withAttributes`	boolean	Include attributes in results	true
`withMetadata`	boolean	Include metadata (owner, creator, expiry) in results	true
`withPayload`	boolean	Include payload in results (base64 encoded)	true
`validAtBlock`	number	Query state at a specific block number	-

Filter Syntax

The filter parameter uses the arkiv_query expression language:

Operator	Description	Example
`=`	Equality	`status = "active"`
`!=`	Not equal	`status != "deleted"`
`>`, `>=`, `<`, `<=`	Numeric range	`score > 100`
`&&`	Logical AND	`type = "post" && score > 50`
`\|\|`	Logical OR	`status = "active" \|\| status = "pending"`
`!`	Negation	`!(status = "deleted")`
`~`	Glob match	`name ~ "test*"`
`!~`	Negated glob	`name !~ "draft*"`

Synthetic attributes (prefixed with $):

Attribute	Description
`$all`	Match all entities
`$owner`	Current owner address
`$creator`	Original creator address (immutable)
`$key`	Entity key

Filter Examples

# All entities
$all

# By entity key
$key = "0xabc123..."

# By owner or creator
$owner = "0x1234567890abcdef..."
$creator = "0x1234567890abcdef..."

# Attribute equality
status = "active"
type = "post"

# Numeric range
score > 100
price >= 50 && price <= 200

# Compound
project = "myapp" && type = "post" && score > 10

# Glob matching
name ~ "draft*"
!(status = "deleted")

Response Format

{
  "entities": [
    {
      "key": "0x...",
      "owner": "0x...",
      "creator": "0x...",
      "createdAtBlock": "12345",
      "lastModifiedAtBlock": "12350",
      "expiresAtBlock": "99999",
      "contentType": "application/json",
      "payload": "<base64-encoded bytes>",
      "attributes": [
        { "key": "type", "value": "post" },
        { "key": "score", "value": 42 }
      ]
    }
  ],
  "cursor": "0x2a",
  "blockNumber": "12350",
  "count": 1
}

Paginate by passing the returned cursor back as the cursor parameter in the next call. When cursor is absent, there are no more results.

Development

The server uses:

@arkiv-network/sdk — Arkiv TypeScript SDK
@modelcontextprotocol/sdk — MCP Server SDK

Project Structure

arkiv-mcp/
├── src/
│   └── index.ts          # Main server implementation
├── package.json
├── tsconfig.json
└── README.md

License

MIT

Available Tools

1 tool

query_entitiesA

Query entities from an Arkiv database chain using a filter expression. The filter uses a SQL-like syntax: comparisons (=, !=, <, >, <=, >=), logical operators (&& and ||), negation (!), and glob matching (~). Special attributes: $all (match everything), $owner (current owner address), $creator (original creator address, immutable), $key (entity key). Examples: '$all', 'status = "active"', 'score > 100', 'project = "myapp" && status = "active"', '$owner = "0x1234..."', 'name ~ "test*"'

ParametersJSON Schema

Name	Required	Description
`filter`	No	Filter expression. Defaults to "$all" if omitted. Examples: 'status = "active"', 'score > 100 && type = "post"', '$owner = "0xAbc..."', '$creator = "0xDef..."', 'name ~ "prefix*"'
`limit`	No	Maximum number of entities to return (max 200)
`cursor`	No	Pagination cursor returned by a previous query
`withAttributes`	No	Include attributes in results (default: true)
`withMetadata`	No	Include metadata (owner, creator, expiry) in results (default: true)
`withPayload`	No	Include payload in results as base64 (default: true)
`validAtBlock`	No	Query state at a specific block number

TDQS

A4.2/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It explains the filter syntax and special attributes but does not disclose performance implications, rate limits, or confirm that it is read-only. Schema covers some aspects (e.g., limit), but behavioral context is lacking.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-structured paragraph that front-loads the core purpose, then details the filter syntax, special attributes, and examples. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description does not explain return values explicitly, but the tool name and parameters imply entities with requested fields. Pagination cursor is mentioned in schema but not explained in description. Overall, it is fairly complete for a query tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds meaningful context for the 'filter' parameter by detailing the syntax and special attributes ($all, $owner, etc.), which goes beyond the schema. Other parameters are not enhanced, but the main parameter benefits significantly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool queries entities from an Arkiv database chain using a filter expression, with specific SQL-like syntax and special attributes. It is a specific verb-resource pair, and there are no sibling tools to distinguish against.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides examples and syntax details that imply when to use the tool, but does not explicitly state when not to use or mention alternatives. Since there are no sibling tools, the lack of exclusion is less critical.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.9/5.0

Disambiguation5/5

Only one tool exists, so there is no risk of confusion between tools. Perfect disambiguation.

Naming Consistency5/5

With a single tool, there are no naming inconsistencies. The name 'query_entities' follows a clear verb_noun pattern.

Tool Count1/5

A single tool is insufficient for a database server; even if it's query-only, missing CRUD operations severely limits functionality. Extreme mismatch.

Completeness2/5

The server only offers query functionality, omitting essential operations like create, update, or delete. Significant gaps for typical database interaction.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

busabase
com.busabase
Database for your AI agent. Turn its output into data, docs, skills, and apps you can actually use.
Databases Data Platforms Knowledge & Memory
11
Statey
ai.statey
An agent-native database over MCP: shared, validated, structured records in every AI chat.
Databases Knowledge & Memory
2
HokAI B
io.hokai
Query the HokAI catalogue of AI tools, agents, models, companies and infrastructure services.
Search AI & Machine Learning Research & Data
21
Oleander
dev.oleander
The all-in-one data stack for agents. Upload files, run SQL, evolve tables, and render charts.
Databases Data Platforms Data Visualization
2

Related MCP Servers

Supabase MCP Server
Databases Developer Tools Autonomous Agents
CloudMediaServices
A
license
Not graded
quality
D
maintenance
Enables AI assistants to perform CRUD operations on Supabase databases through natural language. Supports advanced filtering, pagination, and safety checks for seamless database interaction.
Updated a year ago (2025-08-10 00:38 UTC)
MIT
TextQL MCP Server
Search Databases
alexandme
A
license
Not graded
quality
D
maintenance
Translates natural language to SQL/GraphQL queries and executes them, enabling AI agents to interact with databases through the Model Context Protocol.
Updated a year ago (2025-07-24 22:16 UTC)
1
Apache 2.0
Enterprise Knowledge Mesh
Search Knowledge & Memory Documentation Access
ashishsantikari
F
license
A
quality
C
maintenance
Enables AI agents to query structured knowledge across enterprise domains (legal, HR, compliance) with metadata-driven filtering and TF-IDF ranking.
Updated 3 months ago (2026-06-17 10:31 UTC)
4
Caseware Procurement Document
RAG Systems Search Databases
luiscanaveral
F
license
Not graded
quality
B
maintenance
Enables AI agents to search, retrieve, and answer grounded questions over procurement documents (invoices, purchase orders, contracts, etc.) using hybrid SQL and vector retrieval.
Updated 2 months ago (2026-06-27 20:41 UTC)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/arrivets/arkiv-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

Arkiv MCP Server

Quick Start

Features

Installation

Usage

Start the server

Environment Variables

Command Line Options

MCP Tool

query_entities

Parameters

Filter Syntax

Filter Examples

Response Format

Development

Project Structure

License

Available Tools

TDQS

TDQS

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Supabase MCP Server

TextQL MCP Server

Enterprise Knowledge Mesh

Caseware Procurement Document

Latest Blog Posts

MCP directory API

`query_entities`