# Gcore Developer Tools > REST API, SDKs, MCP Server, Terraform. ## REST API - [Gcore REST API](https://docs.gcore.com/developer-tools/rest-api/overview.md): Entry point for the Gcore REST API covering authentication, base URLs for all products including Cloud, CDN, DNS and Storage, and a learning path from first call through pagination and SDK usage. - [API basics](https://docs.gcore.com/developer-tools/rest-api/api-basics.md): Foundational concepts for calling the Gcore API from a terminal, including how to install and use curl, how to read JSON responses, how to store the API token as an environment variable, and what HTTP status codes mean. - [Authenticate to the Gcore API](https://docs.gcore.com/developer-tools/rest-api/authentication.md): Create a permanent API token in the Gcore Customer Portal, store it as an environment variable, verify the token, and understand token roles, expiry limits, and SSO account behavior. - [Make the first Gcore API call](https://docs.gcore.com/developer-tools/rest-api/first-api-call.md): Step-by-step walkthrough to obtain a project ID and region ID from the Cloud API, set all three required variables in the terminal, and make a verified first resource call using curl, Python SDK, Go SDK, or JavaScript. - [Asynchronous operations and task polling](https://docs.gcore.com/developer-tools/rest-api/async-operations.md): Gcore Cloud API write operations return a task ID while the operation runs in the background; explains how to poll the task endpoint for completion, read the created resource ID from the response, and handle errors and timeouts. - [Error handling](https://docs.gcore.com/developer-tools/rest-api/error-handling.md): Gcore API error responses contain a machine-readable error type, a human-readable message, and a request ID; covers ValidationError, NotFoundError, QuotaLimitExceed, ForbiddenError, HTTP status codes, and retry strategy. - [Pagination](https://docs.gcore.com/developer-tools/rest-api/pagination.md): Gcore API list endpoints return paginated results using limit and offset query parameters; explains the count and results response structure and shows how to iterate through all pages in curl, Python SDK, Go SDK, and JavaScript. - [API tools](https://docs.gcore.com/developer-tools/rest-api/tools.md): Setup guides for Postman with OpenAPI spec import, HTTPie as a readable curl alternative, VS Code REST Client with dot-http files and dotenv token storage, and Bruno or Insomnia as open-source GUI alternatives. ## SDKs - [Gcore API SDKs](https://docs.gcore.com/developer-tools/sdks/overview.md): Overview of official Gcore API SDKs for Python and Go, JavaScript fetch and axios examples, and a guide for choosing the right client for scripting, automation, or production services. - [Python SDK](https://docs.gcore.com/developer-tools/sdks/python.md): Official Gcore Python SDK for REST API access - installation, client initialization with project and region defaults, method naming patterns, task polling with create-and-poll, automatic pagination, error handling with typed exceptions, retries, timeouts, and async usage with AsyncGcore and aiohttp. - [Go SDK](https://docs.gcore.com/developer-tools/sdks/go.md): Official Gcore Go SDK for REST API access - installation, client initialization, param.Opt and omitzero request field semantics, auto-paging list iterators, error handling with errors.As, retries, per-request and per-retry timeouts, middleware, and accessing raw HTTP response data. ## MCP Server - [Gcore MCP Server overview](https://docs.gcore.com/developer-tools/mcp-server/gcore-mcp-server-overview.md): Deploy Gcore MCP Server to expose CDN, Cloud, DNS, FastEdge, IAM, Security, Storage, Streaming, and WAAP API operations as callable tools for AI assistants via Model Context Protocol, supporting Claude Code, Cursor IDE, and MCP Inspector clients with automatic tool schema loading and multi-step workflow chaining. - [Install and configure Gcore MCP Server](https://docs.gcore.com/developer-tools/mcp-server/install-and-configure-gcore-mcp-server.md): Install Gcore MCP Server using uv package manager, create an API token with product-specific permissions, configure GCORE_API_TOKEN and optional GCORE_PROJECT_ID and GCORE_REGION_ID environment variables, and verify server connectivity via uvx or global installation for Claude Code and Cursor IDE integration. - [Connect Cursor IDE to Gcore MCP Server](https://docs.gcore.com/developer-tools/mcp-server/connect-cursor-to-gcore-mcp-server.md): Configure Cursor IDE 0.40+ to connect Gcore MCP Server with product-specific tool patterns (dns.*, storage.*, cdn.*) under 50-tool limit using Gcore API token in MCP configuration file. - [Connect Claude Code to Gcore MCP Server](https://docs.gcore.com/developer-tools/mcp-server/connect-claude-code-to-gcore-mcp-server.md): Configure Gcore MCP Server in Claude Code by installing uv package manager, authenticating with a Claude Pro/Max/Team/Enterprise account, adding Gcore API token to the MCP configuration file, and verifying connection status with resource queries to enable deferred schema loading for Gcore API operations. - [Available products and tools](https://docs.gcore.com/developer-tools/mcp-server/gcore-mcp-server-available-products-and-tools.md): Access Gcore MCP Server tools organized by product - CDN (85 tools), Cloud compute/storage/networking (350 tools), DNS (35 tools), FastEdge (20 tools), IAM (20 tools), and Storage (40 tools) with resource-specific operations like list, create, update, delete, and product-specific actions via filter patterns. - [Filter tools with GCORE_TOOLS](https://docs.gcore.com/developer-tools/mcp-server/filter-tools-with-gcore-tools.md): Configure GCORE_TOOLS environment variable to filter MCP Server tool exposure using predefined toolsets (account, instances, baremetal, gpu_clusters, networks, security, storage, billing, registries, inference), wildcard patterns (cdn_*, cloud_*), and exact tool names separated by commas to reduce context consumption and improve model tool selection accuracy. - [Explore and debug tools with MCP Inspector](https://docs.gcore.com/developer-tools/mcp-server/test-tools-with-mcp-inspector.md): Configure MCP Inspector to connect to Gcore MCP Server via stdio or HTTP transport, explore available tools filtered by product type (DNS, CDN, Cloud), and manually execute tools with parameters to test behavior before integration with Claude Code. ## Terraform - [Overview](https://docs.gcore.com/developer-tools/terraform/overview.md): Install the Gcore Terraform provider, configure v0 and v2 authentication, and manage Cloud and CDN resources via infrastructure-as-code. - [Get started with Terraform](https://docs.gcore.com/developer-tools/terraform/get-started-with-terraform.md) - [Manage a Terraform project](https://docs.gcore.com/developer-tools/terraform/use-variables-and-organize-a-terraform-project.md) - [Import existing Gcore infrastructure into Terraform](https://docs.gcore.com/developer-tools/terraform/import-existing-gcore-infrastructure-into-terraform.md) - [Migrate from Gcore Terraform provider v0 to v2](https://docs.gcore.com/developer-tools/terraform/migrate-v0-to-v2.md) - [Copy resources across environments](https://docs.gcore.com/developer-tools/terraform/copy-resources-across-environments.md): Replicate Gcore infrastructure across preproduction and production environments using Terraform variables, tfvars files, and workspaces. Applies to CDN, Cloud, and DNS resources with both provider v0 and v2.