data_sources — askPulse MCP Tool
data_sources
(data sources) is one of 23 tools on the
askPulse
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call data_sources from your client
- Claude Code askPulse data_sources run in your project directory
- Claude Desktop askPulse data_sources ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor askPulse data_sources ~/.cursor/mcp.json
- VS Code askPulse data_sources .vscode/mcp.json
- Zed askPulse data_sources ~/.config/zed/settings.json
- Windsurf askPulse data_sources ~/.codeium/windsurf/mcp_config.json
- Cline askPulse data_sources ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI askPulse data_sources ~/.gemini/settings.json
- Grok askPulse data_sources .mcp.json (in your project root)
- ChatGPT askPulse data_sources Settings → Connectors → Advanced → Developer mode
- Claude.ai askPulse data_sources Settings → Connectors → Add custom connector
- LangChain askPulse data_sources pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http askpulse https://askpulse.plantdatabases.org/mcpOther tools on this server
- search_data
- find_germplasm
- find_gene
- genes_in_region
- orthologues
- arabidopsis_function
- legume_gene
- legume_pangene
- legume_genes_in_region
- legume_family
- legume_qtl
- legume_qtl_traits
- lupin_markers
- expression_experiments
- gene_expression
- expression_genes
- search_literature
- get_paper
- gene_pathways
- pathway_genes
- trait_hits
- pulse_gene_view
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.