Give your AI agents secure, structured access to Google Drive data through the Apideck MCP Server. 4 resources across File Storage. Managed auth, normalized schemas, zero custom code.
The Apideck MCP Server gives your agent access to Google Drive through normalized APIs. Same schema, same tools, regardless of provider.
4 resources, each with up to 5 operations. Your agent discovers and executes these on demand.
file_storage_files_alllistfile_storage_files_onegetfile_storage_files_addcreatefile_storage_files_updateupdatefile_storage_files_deletedeletefile_storage_drives_alllistfile_storage_drives_onegetfile_storage_drives_addcreatefile_storage_drives_updateupdatefile_storage_drives_deletedeletefile_storage_folders_alllistfile_storage_folders_onegetfile_storage_folders_addcreatefile_storage_folders_updateupdatefile_storage_folders_deletedeletefile_storage_upload_sessions_alllistfile_storage_upload_sessions_onegetfile_storage_upload_sessions_addcreatefile_storage_upload_sessions_updateupdatefile_storage_upload_sessions_deletedeleteSign up for Apideck and create an application.
Link your Google Drive account through Vault. OAuth is handled for you.
Paste the config into your AI client. Your agent can now access the data.
{
"mcpServers": {
"apideck": {
"url": "https://mcp.apideck.dev/mcp",
"headers": {
"x-apideck-api-key": "YOUR_API_KEY",
"x-apideck-app-id": "YOUR_APP_ID",
"x-apideck-consumer-id": "YOUR_CONSUMER_ID"
}
}
}
}Same MCP server, same schema. Switch providers without changing your agent code.