get_sede — Dadaville MCP Tool Read-only
get_sede
(get sede) is one of 10 tools on the
Dadaville
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_sede from your client
- Claude Code Dadaville get_sede run in your project directory
- Claude Desktop Dadaville get_sede ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Dadaville get_sede ~/.cursor/mcp.json
- VS Code Dadaville get_sede .vscode/mcp.json
- Zed Dadaville get_sede ~/.config/zed/settings.json
- Windsurf Dadaville get_sede ~/.codeium/windsurf/mcp_config.json
- Cline Dadaville get_sede ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Dadaville get_sede ~/.gemini/settings.json
- Grok Dadaville get_sede .mcp.json (in your project root)
- ChatGPT Dadaville get_sede Settings → Connectors → Advanced → Developer mode
- Claude.ai Dadaville get_sede Settings → Connectors → Add custom connector
- LangChain Dadaville get_sede pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http dadaville https://www.dadaville.ch/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.