sprkly_list_profiles — sprkly MCP Tool
sprkly_list_profiles
(sprkly list profiles) is one of 19 tools on the
sprkly
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call sprkly_list_profiles from your client
- Claude Code sprkly sprkly_list_profiles run in your project directory
- Claude Desktop sprkly sprkly_list_profiles ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor sprkly sprkly_list_profiles ~/.cursor/mcp.json
- VS Code sprkly sprkly_list_profiles .vscode/mcp.json
- Zed sprkly sprkly_list_profiles ~/.config/zed/settings.json
- Windsurf sprkly sprkly_list_profiles ~/.codeium/windsurf/mcp_config.json
- Cline sprkly sprkly_list_profiles ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI sprkly sprkly_list_profiles ~/.gemini/settings.json
- Grok sprkly sprkly_list_profiles .mcp.json (in your project root)
- ChatGPT sprkly sprkly_list_profiles Settings → Connectors → Advanced → Developer mode
- Claude.ai sprkly sprkly_list_profiles Settings → Connectors → Add custom connector
- LangChain sprkly sprkly_list_profiles pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http sprkly https://sprkly.app/api/mcpOther tools on this server
- sprkly_add_media_from_url
- sprkly_delete_scheduled_post
- sprkly_draft_post
- sprkly_export_automation_template
- sprkly_get_account_summary
- sprkly_get_analytics
- sprkly_get_billing_summary
- sprkly_get_post_approval_status
- sprkly_get_post_status
- sprkly_get_tiktok_posting_options
- sprkly_import_automation_template
- sprkly_list_connected_social_accounts
- sprkly_list_scheduled_posts
- sprkly_request_post_approval
- sprkly_schedule_post
- sprkly_update_scheduled_post
- sprkly_upload_media
- sprkly_validate_post_policy
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.