Skip to content
Agentmart
Submit a tool

Zektor

Managed Postgres and Valkey hosted in Germany.

Connector by m-akcan · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)★ 1
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/m-akcan-zektor

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Managed Postgres and Valkey hosted in Germany. Agents can create a trial database with no signup.

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 26, 2026.

Tools
9 read · 5 write · 6 delete
Secrets
1 (API keys, tokens or passwords)
Install scripts
None found
Runs as
Node.js package

Tools by what they do 20

Read from the source code; the running server may list different tools.

Read 9 · Look things up without changing anything.

  • get_action
  • get_connection
  • get_instance
  • get_storage
  • list_branches
  • list_instances
  • list_plans
  • list_regions
  • whoami

Write 5 · Create, change, send or run things.

  • create_branch
  • create_ephemeral_role
  • create_instance
  • create_trial_database
  • set_autoscale

Delete 6 · Delete, drop, revoke or wipe things.

  • delete_branch
  • delete_instance
  • promote_branch
  • resize_storage
  • scale_instance
  • set_branch_expiry

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

  • ZEKTOR_TOKEN

Network hosts it talks to 3

  • api.zektor.io · found in code
  • github.com · found in code
  • zektor.io · found in code

Files it touches

  • Your home directory (~)

Tools (20)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • create_branchBranch a PostgreSQL database

    Creates a copy-on-write clone of a PostgreSQL instance: it has the source's data from the moment of branching, and the two diverge independently afterwards. THIS COSTS MONEY — a branch is billed hourly like any instance: on its plan, and on what it writes itself above that plan's included storage at €0.15/GB/month, while it is a branch. Once promoted, it is billed on its full size. Pick a smaller plan than the source when the branch is for a test. Takes about a minute: the clone itself is instant, but a second PostgreSQL has to start. Poll get_instance until status is "active". Branching is …

  • create_ephemeral_roleCreate a temporary PostgreSQL login

    RETURNS A LIVE CREDENTIAL. Creates a PostgreSQL role that stops working by itself after ttl_seconds and is then removed. This is the way to connect to a PostgreSQL instance: passwords are never stored, so get_connection cannot return one. The expiry is enforced by PostgreSQL itself, so the credential dies on time whether or not anything else is running. The password is returned once and exists nowhere else. Treat it as a secret and do not repeat it anywhere it would be stored or logged.

  • create_instanceCreate an instance

    Provisions a database or cache. THIS COSTS MONEY — the plan is billed monthly from creation until the instance is deleted. Storage is not a parameter: it starts at the plan's included storage; grow it later with resize_storage. Creating runs in the background, so this returns an instance id and an actionId immediately. Poll get_action with the actionId until it reports "Success" (the instance is then "active") or "Failure".

  • create_trial_databaseCreate a free trial database

    Creates a PostgreSQL database for the next 60 minutes, with no account or token. Returns a connection string and a claim URL. The connection stops working after connectUntil; the data is deleted after claimUntil unless the user opens the claim URL, signs up and adds a payment method, which moves the data into a database of their own. Give the claim URL to the user: it is shown once. Limits: 200 MB, 3 connections, 30-second statements, no superuser; trusted extensions such as pgcrypto work. At most 3 trials per network per day.

  • delete_branchDelete a branchcan change or delete data

    PERMANENTLY DESTROYS a branch and anything written to it since it was created. The source database is untouched. Only works on branches — it refuses the cluster's default database, which has to be removed with delete_instance instead.

  • delete_instanceDelete an instancecan change or delete data

    PERMANENTLY DESTROYS an instance and all of its data. There is no undo and no backup taken on the way out. Confirm with the user before calling this.

  • get_actionCheck background workread-only

    How the background work started by create_instance, scale_instance or resize_storage is going, by the actionId they return. status is "Running", "Success" or "Failure"; on Failure, errorMessage says why. While it is Running, call this again every few seconds.

  • get_connectionGet connection detailsread-only

    RETURNS A LIVE CREDENTIAL for caches: the connection string includes the password. Treat the result as a secret and do not repeat it anywhere it would be stored or logged. For PostgreSQL there is no password to return — one is shown only when a role is created, and the server does not keep it — so the result carries host, port and database. Use create_ephemeral_role to obtain a usable credential.

  • get_instanceGet one instanceread-only

    Full detail for a single instance, including storage and autoscaling where it applies. Does not include credentials — use get_connection for those.

  • get_storageShow storage and automatic growthread-only

    Size, usage, included storage, what is billed above the plan (net €/month), and automatic growth for a PostgreSQL instance.

  • list_branchesList an instance's branchesread-only

    The instance's cluster: the default database and every branch forked from it. `isDefault` marks the one promotion would replace.

  • list_instancesList instancesread-only

    Every database and cache on the account, with id, name, status, engine and plan.

  • list_plansList available plansread-only

    The plans an instance can be created on or scaled to, with price, engine, memory, storage and the engine versions each one can run. Call this before create_instance or scale_instance rather than guessing a plan name.

  • list_regionsList regionsread-only

    Regions an instance can be created in. `available` is false where there is no capacity right now; creating there will be refused.

  • promote_branchMake a branch the defaultcan change or delete data

    Promotes a branch to be its cluster's default database; the previous default becomes a branch. Nothing is deleted and no data moves — this changes which instance the cluster treats as the original. Connection details do not follow the promotion: each instance keeps its own host, port and credentials.

Show 5 more tools
  • resize_storageGrow storagecan change or delete data

    Grows the storage of a PostgreSQL instance to size_gb (larger than now, at most 1000 GB). Storage only grows: this can't be undone, not even by moving to a smaller plan. Each GB above the plan's included storage costs €0.15/month net, prorated by the hour; get_storage shows the current figures.

  • scale_instanceMove an instance to another plancan change or delete data

    Changes the plan an instance runs on, which changes what it costs. Scaling DOWN reduces memory; storage stays (it never shrinks) and GB above the smaller plan are billed at €0.15/GB/month. If the instance is using more memory than the smaller plan provides, that becomes a problem during the move. Check current usage with get_instance first.

  • set_autoscaleConfigure automatic storage growth

    Turns automatic storage growth on or off for a PostgreSQL instance and sets its limit. When on, at 80% full storage grows to the larger of +5 GB or 70% full, never above limit_gb, which is required to turn it on; each grow is permanent and billed like resize_storage. A limit can be raised or lowered but not cleared. Only the fields you pass are sent, so changing one leaves the other alone.

  • set_branch_expiryChange when a branch expires

    Branches delete themselves after a while, so a forgotten one does not keep costing money. This extends that deadline, or removes it entirely. Removing it is a real decision, not a convenience: a kept branch holds its source's old blocks, which count against the source's storage. When that fills, growing it (by hand or automatically) is what costs, which is not obvious from looking at the branch.

  • whoamiShow the authenticated accountread-only

    Reports which Zektor account the current token belongs to, the API it is talking to, and whether the token came from the environment or the config file.

Signals

Stars
1
Forks
0
Open issues
0
Last commit
Oct 8, 2026 (20 days ago)
Last release
Oct 8, 2026 (20 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name
io.github.m-akcan/zektor
Version
1.7.1
Auth
API key
Packages
npm zektor
License
MIT
Repository
github.com/m-akcan/zektor-cli
Website
zektor.io
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
Official MCP Registrygithub-graphql
Cite this page

Zektor MCP server. Agent Mart. https://agentmart.dev/connectors/m-akcan-zektor (last updated 2026-10-24)