followed_base_updates — okfindex MCP Tool
followed_base_updates
(followed base updates) is one of 115 tools on the
okfindex
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call followed_base_updates from your client
- Claude Code okfindex followed_base_updates run in your project directory
- Claude Desktop okfindex followed_base_updates ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor okfindex followed_base_updates ~/.cursor/mcp.json
- VS Code okfindex followed_base_updates .vscode/mcp.json
- Zed okfindex followed_base_updates ~/.config/zed/settings.json
- Windsurf okfindex followed_base_updates ~/.codeium/windsurf/mcp_config.json
- Cline okfindex followed_base_updates ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI okfindex followed_base_updates ~/.gemini/settings.json
- Grok okfindex followed_base_updates .mcp.json (in your project root)
- ChatGPT okfindex followed_base_updates Settings → Connectors → Advanced → Developer mode
- Claude.ai okfindex followed_base_updates Settings → Connectors → Add custom connector
- LangChain okfindex followed_base_updates pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http okfindex https://okfindex.com/mcpOther tools on this server
- api_index
- search_bundles
- get_bundle
- index_stats
- legislation_status
- search_legislation
- get_legislation
- get_legislation_part
- list_bases
- create_base
- publish_base
- unpublish_base
- get_base
- get_base_usage
- list_base_documents
- get_base_connection
- connect_base_source
- disconnect_base_source
- search_base
- add_base_document
- replace_base_document
- remove_base_document
- get_base_document
- read_base_markdown
- read_base_original
- read_base_image
- read_base_index
- read_base_concept
- read_base_source
- read_base_pdf_source
- read_base_docx_source
- read_base_doc_source
- export_base
- restore_base_version
- delete_base_document_permanently
- list_base_history
- get_base_version
- read_base_version_original
- read_base_version_markdown
- read_base_version_concept
- read_base_version_conversion
- read_base_version_image
- quote_base_document
- list_base_conversions
- get_base_conversion
- remove_base_conversion
- authorize_base_conversion
- ask_base_question
- get_base_answer
- save_base_dataset
- public_list_bases
- public_get_base
- public_list_base_documents
- public_search_base
- public_get_base_document
- public_read_base_markdown
- public_read_base_original
- public_read_base_image
- public_read_base_index
- public_read_base_concept
- public_read_base_source
- public_read_base_pdf_source
- public_read_base_docx_source
- public_read_base_doc_source
- public_export_base
- favorite_ids
- favorite_bundles
- save_favorite
- remove_favorite
- list_collections
- create_collection
- get_collection
- search_collection
- save_collection_base
- remove_collection_base
- publish_collection
- unpublish_collection
- remove_collection
- public_get_collection
- public_search_collection
- team_list_bases
- team_get_base
- team_list_base_documents
- team_search_base
- team_get_base_document
- team_read_base_markdown
- team_read_base_original
- team_read_base_image
- team_read_base_index
- team_read_base_concept
- team_read_base_source
- team_read_base_pdf_source
- team_read_base_docx_source
- team_read_base_doc_source
- team_export_base
- team_get_base_answer
- team_list_collections
- team_get_collection
- team_search_collection
- list_knowledge_teams
- get_base_team
- share_base_team
- unshare_base_team
- get_collection_team
- share_collection_team
- unshare_collection_team
- list_followed_bases
- list_base_updates
- get_base_following
- follow_base
- unfollow_base
- submit_bundles
- pricing
- get_api_x402_legislation
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.