Skip to main content
Glama
RestDB

Codehooks.io MCP Server

by RestDB

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CODEHOOKS_SPACEYesThe specific space name within your Codehooks.io project.
CODEHOOKS_ADMIN_TOKENYesYour Codehooks.io admin token, which can be generated using 'coho add-admintoken'.
CODEHOOKS_PROJECT_NAMEYesThe name of your Codehooks.io project.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
query_collectionB

Query data from a collection. Supports URL-style, regex, and MongoDB-style JSON queries with comparison operators. Can also query system collections like '_hooks' which contains deployment metadata including available API endpoints. Using delete, update or replace is very powerful but also dangerous, so use with caution.

deploy_codeA

Deploy JavaScript code to Codehooks.io project.

MINIMAL WORKING EXAMPLE:

import { app } from 'codehooks-js';

app.get('/hello', (req, res) => {
  res.json({ message: 'Hello, world!' });
});

// MANDATORY: bind to serverless runtime
export default app.init();

INSTANT CRUD BACKEND:

import { app } from 'codehooks-js';

// Creates complete CRUD API for any collection (no schema required)
app.crudlify();

export default app.init();

KEY REQUIREMENTS:

  • Always import from 'codehooks-js'

  • Always end with export default app.init();

  • Use app.get(), app.post(), app.put(), app.delete() for routes

  • For database: const conn = await Datastore.open(); conn.insertOne(collection, data);

  • Use app.crudlify() to create complete CRUD backend with no schema required

  • Package.json will be auto-generated if not provided

DOCUMENTATION:

Note: Codehooks.io has CORS built-in by default, so no additional CORS middleware is needed.

file_uploadC

Upload files to server

file_deleteC

Delete a file from server

file_listC

List files from server

create_indexC

Add field(s) to a query index

drop_indexB

Remove field(s) from a query index

create_collectionC

Create a new collection

drop_collectionB

Delete a collection

add_schemaB

Add a JSON schema to a collection. Provide the schema content as a JSON string.

remove_schemaB

Remove JSON schema from a collection

cap_collectionC

Cap a collection

uncap_collectionB

Remove cap from a collection

importA

Import data from file or content. Provide either 'filepath' (for files inside Docker container) or 'content' (JSON/CSV data as string).

exportA

Export data from collection. If no filepath specified, returns the exported content directly. If filepath specified, saves to file inside Docker container.

kv_getB

Retrieve key-value pair(s) from a space. Supports pattern matching with wildcards.

kv_setB

Set key-value pair in a space with optional TTL and keyspace.

kv_delC

Delete key-value pair in a space.

logsC

Show system logs for a space with filtering and follow options.

docsA

Get comprehensive Codehooks.io documentation and examples. Includes complete ChatGPT prompt, setup instructions, code examples, and API reference.

collectionB

Show collections for space. Lists all collections available in the current space.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 21 tools

Disambiguation5/5

Each tool targets a distinct operation or resource: collections, schemas, indexes, queries, key-value store, files, import/export, logs, etc. Even similar-sounding tools like 'collection' (list) and 'create_collection' are clearly differentiated by their descriptions.

Naming Consistency5/5

All tool names use snake_case consistently and follow a verb_noun pattern (e.g., 'add_schema', 'create_collection', 'file_upload', 'kv_set'). Exceptions like 'collection', 'docs', and 'logs' are short nouns for retrieval, which is a common and predictable convention.

Tool Count4/5

With 21 tools, this is slightly above the typical 3-15 range for MCP servers, but the number is justified by the comprehensive set of operations (database, files, KV store, logs, etc.). The tools are well-scoped and each serves a clear purpose.

Completeness5/5

The tool set covers full lifecycle operations for collections (create, list, drop, cap, uncap), schemas (add, remove), indexes (create, drop), queries, key-value store (set, get, del), files (upload, list, delete), import/export, deployment, logs, and documentation. No obvious gaps are present.

Maintenance

ActivitySlowing
ResponsivenessNo issues