seed_entity — Fine Structure MCP Tool
seed_entity
(seed entity) is one of 84 tools on the
Fine Structure
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call seed_entity from your client
- Claude Code Fine Structure seed_entity run in your project directory
- Claude Desktop Fine Structure seed_entity ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Fine Structure seed_entity ~/.cursor/mcp.json
- VS Code Fine Structure seed_entity .vscode/mcp.json
- Zed Fine Structure seed_entity ~/.config/zed/settings.json
- Windsurf Fine Structure seed_entity ~/.codeium/windsurf/mcp_config.json
- Cline Fine Structure seed_entity ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Fine Structure seed_entity ~/.gemini/settings.json
- Grok Fine Structure seed_entity .mcp.json (in your project root)
- ChatGPT Fine Structure seed_entity Settings → Connectors → Advanced → Developer mode
- Claude.ai Fine Structure seed_entity Settings → Connectors → Add custom connector
- LangChain Fine Structure seed_entity pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http fine-structure https://finestructure.ai/api/mcpOther tools on this server
- create_app
- agency_create_client
- agency_list_clients
- agency_create_client_app
- agency_create_claim_link
- agency_get_claim_status
- update_app
- publish_app
- get_platform_guide
- get_recommended_workflow
- get_job_status
- get_app_status
- get_app_links
- list_app_domains
- set_app_subdomain
- check_subdomain_available
- add_custom_domain
- get_domain_verification
- check_domain_verification
- set_primary_domain
- remove_custom_domain
- get_domain_ssl_status
- configure_domain_redirects
- list_apps
- get_app_files
- read_app_file
- read_app_files
- write_app_file
- patch_app_file
- rename_app_file
- get_app_detail
- get_entities
- query_entity
- create_entity_records
- update_entity_record
- update_entity_records
- delete_entity_records
- get_pages
- get_errors
- get_app_analytics
- get_preview_url
- list_saved_versions
- create_change_set
- add_file_change
- validate_change_set
- apply_change_set
- discard_change_set
- validate_app
- inspect_preview
- get_app_security_context
- set_route_policy
- set_entity_policy
- list_app_members
- invite_app_member
- update_app_member_role
- remove_app_member
- get_app_security_audit
- compare_saved_versions
- compare_current_to_version
- restore_file_from_version
- create_entity_schema
- update_entity_schema
- validate_entity_relationships
- update_entity_metadata
- list_secret_keys
- set_secret
- delete_secret
- list_integrations
- configure_integration
- list_ab_tests
- create_ab_test
- update_ab_test
- delete_ab_test
- get_ab_test_stats
- create_agent
- list_agents
- schedule_agent_task
- list_agent_tasks
- get_agent_whatsapp
- start_owner_phone_verification
- confirm_owner_phone_verification
- attach_agent_whatsapp
- detach_agent_whatsapp
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.