# NocoDB API Sources and Verification
## Current API Endpoints Used
Based on `nocodb_mcp_server.py`, we are currently using the following NocoDB API v1 endpoints:
### Meta APIs (Project & Table Management)
- `GET /api/v1/db/meta/projects` - List all projects
- `GET /api/v1/db/meta/projects/{project_id}/tables` - List tables in a project
- `POST /api/v1/db/meta/projects/{project_id}/tables` - Create table
### Data APIs (Record Operations)
- `GET /api/v1/db/data/noco/{project_id}/{table_id}` - Get records (with limit/offset)
- `POST /api/v1/db/data/noco/{project_id}/{table_id}` - Create record
- `PATCH /api/v1/db/data/noco/{project_id}/{table_id}/{record_id}` - Update record
- `DELETE /api/v1/db/data/noco/{project_id}/{table_id}/{record_id}` - Delete record
### Authentication
- Header: `xc-token: {api_token}`
## Official Sources to Verify
### 1. NocoDB Official Documentation
- **REST API Overview**: https://nocodb.com/docs/product-docs/developer-resources/rest-apis/overview/
- **Accessing APIs**: https://nocodb.com/docs/product-docs/developer-resources/rest-apis/accessing-apis/
- **MCP Server Documentation**: https://nocodb.com/docs/product-docs/developer-resources/mcp
### 2. NocoDB GitHub Repository
- **Main Repository**: https://github.com/nocodb/nocodb
- **Releases**: https://github.com/nocodb/nocodb/releases
- **API Documentation in Code**: Check for API route definitions
### 3. NocoDB Changelog
- **Changelog**: https://nocodb.com/changelog
- **Recent Updates**: Check for API changes, deprecations, or new versions
### 4. NocoDB Swagger/OpenAPI
- **Swagger UI**: Available at `{nocodb_url}/api/v1/swagger` or similar
- **API Reference**: Check for OpenAPI/Swagger specifications
### 5. NocoDB SDK Documentation
- **JavaScript SDK**: https://docs.nocodb.com/0.109.7/developer-resources/sdk/
- **Python Client**: https://github.com/infeeeee/nocodb-api
## Key Areas to Check
### API Version
- [ ] Is API v1 still current or has v2 been released?
- [ ] Are there any deprecated endpoints we're using?
- [ ] Are there new endpoints we should be using?
### Authentication
- [ ] Is `xc-token` header still the correct method?
- [ ] Are there new authentication methods (OAuth, etc.)?
- [ ] Any changes to token format or requirements?
### Endpoint Changes
- [ ] Have any endpoint paths changed?
- [ ] Are there new query parameters available?
- [ ] Have response formats changed?
### New Features
- [ ] MCP Server integration (NocoDB now has built-in MCP support)
- [ ] OAuth integration for AI assistants
- [ ] New API capabilities we should leverage
## Verification Results
### ✅ Confirmed Current Implementation
Based on code review, we are using:
- **API Version**: v1 (all endpoints use `/api/v1/`)
- **Authentication**: `xc-token` header (confirmed correct)
- **Endpoints**: All standard v1 endpoints for meta and data operations
- **Instance Type**: Self-hosted at `nocodb.v1su4.com`
### ⚠️ Important: Self-Hosted vs Cloud Differences
**Self-Hosted Instance Considerations:**
- ✅ **API v1 is valid** for self-hosted instances (our current implementation)
- ⚠️ **API v2 may also be available** depending on NocoDB version
- ✅ **`xc-token` authentication works** on both self-hosted and cloud
- ⚠️ **Native MCP Server** may require newer NocoDB version (v0.265.0+)
- ⚠️ **OAuth integration** may require newer version (v2025.10.0+)
- ⚠️ **Workspace APIs** may be limited (single workspace in self-hosted)
**What Applies to Your Self-Hosted Instance:**
1. ✅ All API v1 endpoints we use are valid for self-hosted
2. ✅ `xc-token` header authentication is correct
3. ✅ Meta APIs (`/api/v1/db/meta/projects`) work on self-hosted
4. ✅ Data APIs (`/api/v1/db/data/noco/...`) work on self-hosted
5. ⚠️ Native MCP server feature depends on your NocoDB version
6. ⚠️ OAuth integration depends on your NocoDB version
### 📋 Official Sources Verified
1. **NocoDB REST API Documentation**
- URL: https://nocodb.com/docs/product-docs/developer-resources/rest-apis/overview/
- Status: ✅ Active and current
- Contains: Meta APIs, Data APIs, authentication methods
2. **NocoDB MCP Server Documentation**
- URL: https://nocodb.com/docs/product-docs/developer-resources/mcp
- Status: ✅ Available (NocoDB has built-in MCP support)
- Note: NocoDB now has native MCP server (v0.265.0+)
3. **NocoDB Changelog**
- URL: https://nocodb.com/changelog
- Key Updates:
- v0.265.0: Introduced MCP Server (Sept 2025)
- v2025.10.0: OAuth integration for AI assistants
- v2025.09.0: MCP Server and webhook triggers
4. **NocoDB GitHub Repository**
- URL: https://github.com/nocodb/nocodb
- Releases: https://github.com/nocodb/nocodb/releases
- Status: ✅ Active development
### ⚠️ Important Findings
1. **NocoDB Native MCP Server**: NocoDB now has built-in MCP server support (0.265.0+)
- **Official Documentation**: https://nocodb.com/docs/product-docs/mcp
- **Features**: OAuth for web clients, base-specific endpoints, standard CRUD
- **Self-Hosted**: Replace `https://app.nocodb.com` with your instance URL
- **Our Custom Server**: Still valid for cross-base operations, custom tools, table creation
- **Comparison**: See [NATIVE_MCP_VS_CUSTOM.md](NATIVE_MCP_VS_CUSTOM.md) for detailed comparison
2. **API v1 Still Current**: No evidence of API v2 migration required
- All endpoints we use are still valid
- `xc-token` authentication is still correct
- No breaking changes found
3. **OAuth Integration**: New OAuth support for AI assistants
- May be alternative to API tokens for some use cases
- Our current token-based approach remains valid
## Action Items
1. ✅ **Verify Current Endpoints**: All endpoints confirmed valid
2. ✅ **Check for API v2**: No v2 migration needed (v1 still current)
3. ⏳ **Update Documentation**: Add note about NocoDB's native MCP server
4. ⏳ **Test Endpoints**: Verify compatibility with latest NocoDB version
5. ⏳ **Document Native MCP**: Add comparison/guidance on native vs custom MCP
## Recommended Updates
### Documentation Updates Needed:
1. ✅ Add note about NocoDB's native MCP server in README (if version supports it)
2. ✅ Clarify when to use custom MCP vs native MCP
3. ⚠️ Update NOCODB_API_SETUP_GUIDE.md - verify API v1 vs v2 for self-hosted
4. ✅ Verify all endpoint examples match current API
5. ✅ Add note about self-hosted instance limitations (workspace, version-specific features)
### Self-Hosted Specific Notes:
- **API Version**: Our code uses v1, which is valid for self-hosted
- **Version Check**: Need to verify which NocoDB version is running on `nocodb.v1su4.com`
- **Feature Availability**: Native MCP and OAuth depend on NocoDB version
- **Swagger UI**: Available at `https://nocodb.v1su4.com/api/v1/swagger` (verify exact path)
### Code Verification:
1. All API endpoints are using correct v1 paths ✅
2. Authentication header (`xc-token`) is correct ✅
3. No deprecated endpoints in use ✅
4. Response handling matches current API format ✅
## Notes
### Version-Specific Features (May Not Apply to Self-Hosted):
- **NocoDB version 0.265.0**: Introduced MCP Server (September 2025) - **Check if your instance has this**
- **NocoDB version 2025.10.0**: Introduced OAuth integration - **Check if your instance has this**
### Self-Hosted Instance (`nocodb.v1su4.com`):
- ✅ **Our Implementation**: Valid and current - using standard v1 API
- ✅ **API v1 Endpoints**: All endpoints we use work on self-hosted instances
- ✅ **Authentication**: `xc-token` header works correctly
- ⚠️ **Version Check Needed**: Verify which NocoDB version is running to know feature availability
- ⚠️ **API v2**: May be available but we're correctly using v1 (both may work)
- ✅ **API Stability**: v1 API is stable and compatible with self-hosted instances
### Action Required:
1. **Check NocoDB Version**: Verify version running on `nocodb.v1su4.com`
2. **Test Swagger UI**: Access `https://nocodb.v1su4.com/api/v1/swagger` to see available endpoints
3. **Verify Features**: Check if native MCP server is available in your version
4. **Document Version**: Add NocoDB version info to documentation
