MCP server exposing ownCloud Infinite Scale (oCIS) as 80 AI-accessible tools
{
"mcpServers": {
"ocis-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server exposing ownCloud Infinite Scale (oCIS) as 80 AI-accessible tools
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
Apache-2.0. View license →
Is it maintained?
Last commit 0 days ago.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
MCP Security Weekly
Get CVE alerts and security updates for Ocis Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A standalone Model Context Protocol (MCP) server that exposes ownCloud Infinite Scale (oCIS) as a set of MCP tools. It enables AI assistants such as Claude to manage users, groups, spaces, files, shares, and more through natural language.
New to this? Check out the Getting Started Guide -- a step-by-step walkthrough
for connecting the MCP server with Claude Desktop or Ollama on Mac, Windows, and Linux. Includes a
setup script (install.sh) that detects your system and helps you configure everything.
This server is intentionally separate from the oCIS codebase:
flowchart LR
subgraph "AI Host"
A[Claude Desktop / Claude Code]
end
subgraph "MCP Server"
B[ocis-mcp-server]
B1[Tools - 80 tools]
B2[Resources - 5 endpoints]
B3[Prompts - 4 templates]
B --> B1
B --> B2
B --> B3
end
subgraph "oCIS Instance"
C[LibreGraph API]
D[WebDAV]
E[OCS API]
end
A -- "MCP (stdio / HTTP)" --> B
B1 -- "HTTPS" --> C
B1 -- "HTTPS" --> D
B1 -- "HTTPS" --> E
go build -o ocis-mcp-server ./cmd/ocis-mcp-server
Or use Make:
make build
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json
on macOS):
{
"mcpServers": {
"ocis": {
"command": "/path/to/ocis-mcp-server",
"env": {
"OCIS_MCP_OCIS_URL": "https://your-ocis-instance.example.com",
"OCIS_MCP_APP_TOKEN_USER": "admin",
"OCIS_MCP_APP_TOKEN_VALUE": "your-app-token-here"
}
}
}
}
Add to .mcp.json in your project root or ~/.claude/mcp.json globally:
{
"mcpServers": {
"ocis": {
"command": "/path/to/ocis-mcp-server",
"env": {
"OCIS_MCP_OCIS_URL": "https://your-ocis-instance.example.com",
"OCIS_MCP_APP_TOKEN_USER": "admin",
"OCIS_MCP_APP_TOKEN_VALUE": "your-app-token-here"
}
}
}
}
App tokens provide scoped, revocable credentials ideal for MCP server use:
export OCIS_MCP_OCIS_URL="https://ocis.example.com"
export OCIS_MCP_APP_TOKEN_USER="admin"
export OCIS_MCP_APP_TOKEN_VALUE="<token-value>"
For environments using OpenID Connect:
export OCIS_MCP_OCIS_URL="https://ocis.example.com"
export OCIS_MCP_AUTH_MODE="oidc"
export OCIS_MCP_OIDC_ACCESS_TOKEN="<access-token>"
Optionally, if you need token refresh:
export OCIS_MCP_OIDC_ISSUER="https://idp.example.com"
export OCIS_MCP_OIDC_CLIENT_ID="ocis-mcp"
export OCIS_MCP_OIDC_CLIENT_SECRET="<client-secret>"
| Variable | Required | Default | Description |
|---|---|---|---|
OCIS_MCP_OCIS_URL | Yes | -- | Base URL of the oCIS instance (e.g., https://ocis.example.com) |
OCIS_MCP_AUTH_MODE | No | auto-detect | Authentication mode: app-token or |