Skip to main content
Glama

Knowledge MCP Server

by sven-borkert

sync_storage

Manually trigger git synchronization for the Knowledge MCP Server datastore to backup changes, resolve sync issues, or ensure data persistence before major operations. Handles uncommitted changes and push failures effectively.

Instructions

Force git add, commit, and push all changes in the knowledge datastore.

When to use this tool:

  • Manually triggering backup to remote

  • Ensuring changes are persisted

  • Before major operations

  • Resolving sync issues

  • Explicit backup request

Key features:

  • Commits ALL uncommitted changes

  • Pushes to configured remote

  • Auto-generates commit message

  • Handles push failures gracefully

  • Forces synchronization

You should:

  1. Check storage_status first

  2. Use when auto-sync fails

  3. Verify remote is configured

  4. Handle push failures appropriately

  5. Use sparingly (auto-sync usually works)

DO NOT use when:

  • No changes to commit

  • Remote not configured

  • Auto-sync is working fine

Returns: {success: bool, message: str, files_committed: int, pushed: bool, push_error?: str, commit_message: str}

Input Schema

NameRequiredDescriptionDefault

No arguments

Input Schema (JSON Schema)

{ "$schema": "http://json-schema.org/draft-07/schema#", "additionalProperties": false, "properties": {}, "type": "object" }

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/sven-borkert/knowledge-mcp'

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