# Periscope MCP server

> Brokers MCP clients to a live Neovim configuration to access LSPs, formatters, linters, and DAP modules directly.

- Repository: https://github.com/qompassai/periscope
- Page: https://hostedmcp.org/servers/qompassai/periscope
- Transport: stdio
- Stars: 0
- Latest version: 1.0.0

## Tools (16)

- `attention_alignment`
- `attention_decide`
- `attention_focus`
- `attention_publish`
- `broker_status`
- `get_definition`
- `get_diagnostics`
- `get_document_symbols`
- `get_hover`
- `get_references`
- `list_dap`
- `list_formatters`
- `list_linters`
- `list_servers`
- `run_format`
- `run_lint`

## FAQ

### Does Periscope write changes to my files?

No, formatting is applied only to the brokered editor's buffer and returned as text; the file on disk is never written.

### How does Periscope connect to my existing Neovim session?

You can use the Attach mode by providing the socket path of a running Neovim instance started with the --listen flag.

### Is there any network exposure in Periscope?

No, it uses stdio transport only, meaning nothing listens on a network port.

### What happens if an LSP server is slow to respond?

The tools poll inside the editor while servers report in-flight progress, allowing for real answers from slow servers like rust-analyzer.
